View 298020-002_4898393.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

intel ? 840 chipset: 82840 memory controller hub (mch) datasheet september 2000 document number: 298020-002 r
2 datasheet information in this document is provided in connection with intel products. no license, express or implied, by estoppel or oth erwise, to any intellectual property rights is granted by this document. except as provided in intel?s terms and conditions of sale for such products, inte l assumes no liability whatsoever, and intel disclaims any express or implied warranty, relating to sale and/or use of intel products including liabil ity or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. intel products are not intended for use in medical, life saving, or life sustaining applications. intel may make changes to specifications and product descriptions at any time, without notice. designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." int el reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. the intel? 82840 mch may contain design defects or errors known as errata which may cause the product to deviate from published specifications. current characterized errata are available on request. contact your local intel sales office or your distributor to obtain the latest specifications and before placing your product o rder. i 2 c is a 2-wire communications bus/protocol developed by philips. smbus is a subset of the i 2 c bus/protocol and was developed by intel. implementations of the i 2 c bus/protocol may require licenses from various entities, including philips electronics n.v. and north american philips corpor ation. alert on lan is a result of the intel-ibm advanced manageability alliance and a trademark of ibm copies of documents which have an ordering number and are referenced in this document, or other intel literature, may be obtain ed from: intel corporation www.intel.com or call 1-800-548-4725 *third-party brands and names are the property of their respective owners. copyright ? intel corporation 2000
82840 mch r datasheet 3 contents 1. overview.................................................................................................................... .................13 1.1. intel ? 840 chipset system architecture .........................................................................13 1.2. 82840 mch overview ....................................................................................................16 1.3. terminology ............................................................................................................... ....18 2. signal description.......................................................................................................... .............21 2.1. host interface signals .................................................................................................... 22 2.2. direct rambus* interface a ...........................................................................................24 2.3. direct rambus* interface b ...........................................................................................25 2.4. hub interface a signals .................................................................................................26 2.5. hub interface b signals..................................................................................................2 6 2.6. agp interface signals....................................................................................................2 6 2.6.1. agp addressing signals ...................................................................................26 2.6.2. agp flow control signals .................................................................................27 2.6.3. agp status signals ...........................................................................................28 2.6.4. agp clocking signals?strobes .......................................................................28 2.6.5. agp frame# signals.......................................................................................29 2.7. clocks, reset, and miscellaneous .................................................................................31 2.8. voltage references, pll power ....................................................................................32 2.9. strap signals............................................................................................................. .....33 3. register description ........................................................................................................ ...........35 3.1. register nomenclature and access attributes ..............................................................35 3.2. pci configuration space access ...................................................................................36 3.3. i/o mapped registers ....................................................................................................39 3.3.1. conf_addr ? configuration address register ..............................................39 3.3.2. conf_data?configuration data register.....................................................40 3.4. host-hub interface a bridge/dram controller device registers (device 0) ................41 3.4.1. vid?vendor identification register (device 0) ................................................44 3.4.2. did?device identification register (device 0).................................................44 3.4.3. pcicmd?pci command register (device 0) .................................................45 3.4.4. pcists?pci status register (device 0).........................................................46 3.4.5. rid?revision identification register (device 0)..............................................47 3.4.6. subc?sub-class code register (device 0)...................................................47 3.4.7. bcc?base class code register (device 0)....................................................47 3.4.8. mlt?master latency timer register (device 0) .............................................48 3.4.9. hdr?header type register (device 0) ..........................................................48 3.4.10. ?aperture base configuration register (device 0)..........................................48 3.4.11. svid?subsystem vendor id (device 0) ..........................................................50 3.4.12. sid?subsystem id (device 0) .........................................................................50 3.4.13. capptr?capabilities pointer (device 0) ........................................................50 3.4.14. gar[15:0]?rdram group architecture register (device 0)..........................51 3.4.15. mchcfg?mch configuration register (device 0).........................................52 3.4.16. fdhc?fixed dram hole control register (device 0)....................................53 3.4.17. pam0?pam6?programmable attribute map registers (device 0) ................54 3.4.18. gba0?gba15?rdram group boundary address register (device 0) ........57 3.4.19. rdps?rdram pool sizing register (device 0) .............................................58
4 datasheet 3.4.20. drd?rdram device register data register (device 0) .............................. 59 3.4.21. ricm?rdram initialization control management register (device 0).......... 59 3.4.22. mch expansion rac a/b configuration registers .......................................... 61 3.4.23. smram?system management ram control register (device 0) ................ 61 3.4.24. esmramc?extended system management ram control register (device 0) ......................................................................................................... . 62 3.4.25. acapid?agp capability identifier register (device 0) .................................. 63 3.4.26. agpstat?agp status register (device 0)................................................... 64 3.4.27. agpcmd?agp command register (device 0) ............................................. 65 3.4.28. agpctrl?agp control register (device 0) ................................................. 66 3.4.29. apsize?aperture size (device 0) .................................................................. 66 3.4.30. attbase ? aperture translation table base register (device 0) ................ 67 3.4.31. amtt?agp interface multi-transaction timer register (device 0) .............. 67 3.4.32. lptt?low priority transaction timer register (device 0)............................. 68 3.4.33. rdtr?rdram timing register (device 0) ................................................... 69 3.4.34. rdcr?rdram refresh control register (device 0)..................................... 70 3.4.35. tom?top of low memory register (device 0)............................................... 71 3.4.36. errsts?error status register (device 0)..................................................... 71 3.4.37. errcmd?error command register (device 0) ............................................. 73 3.4.38. smicmd?smi command register (device 0)................................................ 75 3.4.39. scicmd?sci command register (device 0)................................................. 77 3.4.40. skpd?scratchpad data (device 0) ................................................................ 78 3.4.41. herrctl_sts?host error control/status register (device 0) .................... 79 3.4.42. derrctl_sts?dram error control/status register (device 0) ................ 80 3.4.43. eap?error address pointer register (device 0)............................................. 80 3.4.44. agpbctrl?agp buffer strength control register ....................................... 81 3.4.45. agpappend?agp append disable register................................................ 81 3.4.46. gtlnclamp?gtl n clamp disable register............................................... 81 3.5. agp bridge registers (device 1) .................................................................................. 82 3.5.1. vid1?vendor identification register (device 1).............................................. 83 3.5.2. did1?device identification register (device 1) .............................................. 83 3.5.3. pcicmd1?pci-pci command register (device 1) ....................................... 84 3.5.4. pcists1?pci-pci status register (device 1) ............................................... 85 3.5.5. rid1?revision identification register (device 1) ........................................... 85 3.5.6. subc1?sub-class code register (device 1) ................................................ 86 3.5.7. bcc1?base class code register (device 1) ................................................. 86 3.5.8. mlt1?master latency timer register (device 1) .......................................... 86 3.5.9. hdr1?header type register (device 1) ........................................................ 86 3.5.10. pbusn1?primary bus number register (device 1)....................................... 87 3.5.11. sbusn1?secondary bus number register (device 1) .................................. 87 3.5.12. subusn1?subordinate bus number register (device 1) ............................. 87 3.5.13. smlt1?secondary master latency timer register (device 1) ...................... 88 3.5.14. iobase1?i/o base address register (device 1) ........................................... 88 3.5.15. iolimit1?i/o limit address register (device 1)............................................ 89 3.5.16. ssts1?secondary pci-pci status register (device 1)................................. 89 3.5.17. mbase1?memory base address register (device 1).................................... 90 3.5.18. mlimit1?memory limit address register (device 1) .................................... 91 3.5.19. pmbase1?prefetchable memory base address register (device 1) ............ 91 3.5.20. pmlimit1?prefetchable memory limit address register (device 1)............. 92 3.5.21. bctrl1?pci-pci bridge control register (device 1) ................................... 92 3.5.22. errcmd1?error command register (device 1) ........................................... 94
82840 mch r datasheet 5 3.6. hub interface b bridge registers (device 2) .................................................................95 3.6.1. vid2?vendor identification register (device 2) ..............................................96 3.6.2. did2?device identification register (device 2)...............................................96 3.6.3. pcicmd2?pci-pci command register (device 2)........................................97 3.6.4. pcists2?pci-pci status register (device 2)................................................98 3.6.5. rid2?revision identification register (device 2)............................................98 3.6.6. subc2?sub-class code register (device 2).................................................99 3.6.7. bcc2?base class code register (device 2)..................................................99 3.6.8. mlt2?master latency timer register (device 2) ...........................................99 3.6.9. hdr2?header type register (device 2) ........................................................99 3.6.10. pbusn2?primary bus number register (device 2) .....................................100 3.6.11. sbusn2?secondary bus number register (device 2) ................................100 3.6.12. subusn2?subordinate bus number register (device 2)............................100 3.6.13. smlt2?secondary master latency timer register (device 2) ....................100 3.6.14. iobase2?i/o base address register (device 2) .........................................101 3.6.15. iolimit2?i/o limit address register (device 2) ..........................................101 3.6.16. ssts2?secondary pci-pci status register (device 2) ...............................102 3.6.17. mbase2?memory base address register (device 2) ..................................103 3.6.18. mlimit2?memory limit address register (device 2) ...................................103 3.6.19. pmbase2?prefetchable memory base address register (device 2) ..........104 3.6.20. pmlimit2?prefetchable memory limit address register (device 2) ...........104 3.6.21. bctrl2?pci-pci bridge control register (device 2) ..................................105 3.6.22. errcmd2?error command register (device 2) .........................................106 4. system address map.......................................................................................................... ......107 4.1. memory address ranges.............................................................................................107 4.1.1. dos compatibility area...................................................................................108 4.1.2. extended memory area...................................................................................110 4.1.3. agp memory address ranges .......................................................................112 4.1.4. agp dram graphics aperture .......................................................................113 4.1.5. system management mode (smm) memory range .......................................113 4.1.5.1. smm space definition.......................................................................114 4.1.5.2. smm space restrictions ...................................................................114 4.1.6. memory shadowing.........................................................................................115 4.1.7. i/o address space ..........................................................................................115 4.1.7.1. agp i/o address mapping ................................................................115 4.1.8. mch decode rules and cross-bridge address mapping...............................116 4.1.8.1. the hub interface a decode rules...................................................116 4.1.8.2. the hub interface b decode rules...................................................116 4.1.8.3. agp interface decode rules ............................................................117 4.1.8.4. legacy vga ranges.........................................................................118
6 datasheet 5. functional description...................................................................................................... ........ 119 5.1. host interface ............................................................................................................ .. 119 5.1.1. frame buffer memory support ....................................................................... 125 5.2. agp interface ............................................................................................................. . 125 5.2.1. agp target operations .................................................................................. 125 5.2.2. agp transaction ordering ............................................................................. 127 5.2.3. agp electricals ............................................................................................... 127 5.2.4. the differences between agp frame# and pci-66 devices ...................... 127 5.2.5. 4x agp protocol ............................................................................................. 127 5.2.6. fast writes...................................................................................................... 128 5.2.7. agp universal connector............................................................................... 128 5.2.8. agp frame# transactions on agp ............................................................. 128 5.2.8.1. mch initiator and target operations................................................ 129 5.2.8.2. mch retry/disconnect conditions ................................................... 131 5.2.8.3. delayed transaction ......................................................................... 131 5.3. rdram interface ........................................................................................................ 132 5.3.1. rdram organization and configuration ........................................................ 134 5.3.1.1. rules for populating rdram devices ............................................. 135 5.3.1.2. rdram cmos signals description and usage............................... 136 5.3.1.3. direct rdram core refresh............................................................ 138 5.3.1.4. direct rdram current calibration ................................................... 138 5.3.2. direct rdram command encoding............................................................... 138 5.3.2.1. row packet (rowa/rowr) ........................................................... 139 5.3.2.2. column packet (colc/colx) ......................................................... 141 5.3.2.3. data packet ...................................................................................... 142 5.3.3. direct rdram register programming ........................................................... 143 5.3.4. direct rdram operating states .................................................................... 143 5.3.5. rdram power management.......................................................................... 144 5.3.6. data integrity................................................................................................... 145 5.3.7. rdram array thermal management............................................................. 145 5.4. system reset .............................................................................................................. 146 6. ballout and package information ............................................................................................. 147 6.1. mch ball list ............................................................................................................. .. 147 6.2. package information.................................................................................................... 154 6.2.1. 82840 rsl nomalized trace length data ..................................................... 156 6.3. initialization sequence................................................................................................. 16 0 6.4. xor chains................................................................................................................ . 161
82840 mch r datasheet 7 figures figure 1. intel ? 840 chipset system block diagram ................................................................14 figure 2. pam registers........................................................................................................ ...55 figure 3. system address map ..............................................................................................107 figure 4. detailed dos compatible area address map.........................................................110 figure 5. detailed extended memory range address map ...................................................110 figure 6. single channel-pair mode .......................................................................................132 figure 7. multiple channel-pair mode.....................................................................................133 figure 8. rdram devices sideband cmos signal configuration on rambus* channel a ................................................................................................136 figure 9. mrh-r sideband cmos signal configuration on rambus* channel a.................137 figure 10. 82840 mch reset .................................................................................................146 figure 11. mch ballout (top view, left side)........................................................................148 figure 12. mch ballout (top view, right side) .....................................................................149 figure 13. 82840 mch bga package dimensions (top and side views) ............................154 figure 14. 82840 mch bga package dimensions (bottom view) ........................................155 figure 15. xor-tree chain....................................................................................................15 9 figure 16. xor chain test mode initialization.......................................................................160
8 datasheet tables table 1. maximum memory vs dram densities ..................................................................... 17 table 2. mch configuration space (device 0) ........................................................................ 41 table 3. attribute bit assignment............................................................................................. 5 4 table 4. pam registers and associated memory segments .................................................. 55 table 5. mch configuration space (device 1) ........................................................................ 82 table 6. mch configuration space (device 2) ........................................................................ 95 table 7. memory segments and their attributes.................................................................... 108 table 8. p6 bus transactions supported by the mch .......................................................... 119 table 9. types of responses supported by the mch ........................................................... 121 table 10. types of special cycles supported by the mch ................................................... 124 table 11. agp commands supported by the mch when acting as an agp target ........... 126 table 12. fast write register programming ......................................................................... 128 table 13. pci commands supported by the mch when acting as a frame# target ....... 129 table 14. maximum memory supported for various configurations .................................... 133 table 15. direct rdram device configurations ................................................................... 134 table 16. rdram device grouping ...................................................................................... 135 table 17. sideband cmos signal description ...................................................................... 137 table 18. cmd signal value decode..................................................................................... 137 table 19. rowa packet for activating (sensing) a row (i.e., av = 1) .................................. 139 table 20. rowr packet for other operations (i.e., av = 0) .................................................. 139 table 21. colc packet ......................................................................................................... 1 41 table 22. colc packet field encodings............................................................................... 141 table 23. colx packet (m = 0) ............................................................................................. 142 table 24. colm packet and colx packet field encodings ................................................ 142 table 25. data packet.......................................................................................................... .. 142 table 26. dram operating states......................................................................................... 143 table 27. rdram power management states...................................................................... 144 table 28. mch alphabetical ballout list ................................................................................ 150 table 29. package dimensions ............................................................................................. 155 table 30. xor chain #0 connections ................................................................................... 161 table 31. xor chain #1 connections ................................................................................... 161 table 32. xor chain #2 connections ................................................................................... 162 table 33. xor chain #3 connections ................................................................................... 162 table 34. xor chain #4 connections ................................................................................... 163 table 35. xor chain #5 connections ................................................................................... 164 table 36. xor chain #6 connections ................................................................................... 164
82840 mch r datasheet 9 revision history rev. draft/changes date -001 ? initial release october 1999 -002 ? minor edits throughout for clarity. ? removed references to mrh-s and sdram ? removed references to using two mrh-rs per channel. september 2000
10 datasheet this page is left intentionally blank.
82840 mch r datasheet 11 intel ? 82840 mch product features processor/host bus support ? supports up to two pentium ? ii processors or pentium ? iii processors at 100 mhz or 133 mhz system bus frequency ? supports full symmetric multiprocessor (smp) protocol ? supports 32- or 36-bit host bus addressing ? supports 8 deep in-order queue ? ecc protection on fsb data signals ? ierr and berr signals generate sci/serr ? parity protection on address/response signals memory controller?direct rambus* support ? direct support for dual direct rambus* channels operating in lock-step: supports 300 mhz, 400 mhz ? supports 64mb, 128mb, 256mb rdram devices ? maximum memory array size up to 1 gb using 64mb, 2 gb using 128mb, 4 gb using 256mb ? supports up to 64 direct rambus* devices without using mrh-rs ? supports up to four rambus* channels using two external memory repeater hubs for rdram devices (mrh-r) power management ? smram space remapping to a0000h?bffffh (128 kb) ? supports extended smram space above 256 mb, additional 128 kb / 256 kb / 512 kb / 1 mb tseg from top of memory, cacheable (cacheability controlled by processor) ? suspend to ram support memory controller?configurable optional ecc operation ? ecc with single bit error correction and multiple bit error detection ? single bit errors corrected and written back to memory (scrubbing) accelerated graphics port (agp) interface ? supports a single agp device (either via a connector or on the motherboard) ? supports agp 2.0 including 4x agp data transfers and 2x/4x fast write protocol ? agp universal connector support via dual mode buffers to allow agp 2.0 3.3v or 1.5v signaling hub interface a to ich?high speed interconnect between mch and ich (266 mb/sec) hub interface b to p64h?high speed interconnect between mch and p64h (533 mb/sec) arbitration ? distributed arbitration model for optimum concurrency support ? concurrent operations of host, hub interface, agp, and memory buses supported via dedicated arbitration and data buffering logic process/package ? 544 mbga the intel ? 82840 memory controller hub may contain design defects or errors known as errata which may cause the product to deviate from published specifications. current characterized errata are available on request.
12 datasheet simplified block diagram mch_blk.vs d ha[35:3]# hd[63:0]# ads# bnr# bpri# ap[1:0]# berr# breq0# dbsy# dep[7:0]# defer# drdy# hit# hitm# hlock# hreq[4:0]# htrdy# ierr# rp# rsp# rs[2:0]# cpurst# system bus interface agp interface clocks, reset, and test cpuclk clk66 rclkout[a:b] hclkout[a:b] rstin# test# overt# voltage references, power, ground gtlref[a:b] agprcomp cha_ref[1:0] chb_ref[1:0] agpref hlaref hlbref vddq vcc1_8 vtt vss pipe# sba[7:0] st[2:0] rbf# wbf# ad_stb0, ad_stb0# ad_stb1, ad_stb1# sb_stb, sb_stb# g_ad[31:0] g_c/be[3:0]# g_frame# g_trdy# g_irdy# g_req# g_devsel# g_gnt# g_par g_stop# g_serr# hla[11:0] hla_stb, hla_stb# hlazcomp hub interface a hlb[19:0] hlb_stb[1:0], hlb_stb[1 hlbrcomp hub interface b cha_dqa[8:0] cha_dqb[8:0] cha_rq[7:5] or cha_row[2:0] cha_rq[4:0] or cha_col[4:0] cha_ctm, cha_ctm# cha_cfm, cha_cfm# cha_cmd cha_sck cha_sio cha_exp[1:0] system memory direct rambus interface a chb_dqa[8:0] chb_dqb[8:0] chb_rq[7:5] or chb_row[2:0] chb_rq[4:0] or chb_col[4:0] chb_ctm, chb_ctm# chb_cfm, chb_cfm# chb_cmd chb_sck chb_sio chb_exp[1:0] system memory direct rambus interface b
82840 mch r datasheet 13 1. overview the intel ? 840 chipset is a high-bandwidth chipset designed for workstation and server platforms based on intel ? pentium ? ii processor / intel ? pentium ? iii processor architectures. the chipset contains two main components and additional optional components that provide expansion capability. the 82840 memory controller hub (mch) provides the system bus interface, memory controller, agp interface, hub interface for i/o, and hub interface for pci bus expansion. this document describes the 82840 memory controller hub (mch). section 1.1, intel ? 840 chipset system architecture, provides an overview of each of the components of the intel ? 840 chipset. 1.1. intel ? 840 chipset system architecture the intel ? 840 chipset is optimized for the intel ? pentium ? ii processor and intel ? pentium ? iii processor architectures. the intel ? 840 chipset allows flexibility for dual and multi-processor configurations with 100 mhz and 133 mhz system buses. the intel ? 840 chipset consists of 2 main components: 82840 memory controller hub (mch), and 82801aa i/o controller hub (ich). architectural expansion is provided with the memory expansion card and pci 64-bit hub. the 82803aa memory repeater hub (mrh-r) provides memory expansion capabilities for rdram channels. the 82806aa pci 64 hub (p64h) provides pci bridging functions between the hub interface and pci bus. the intel ? 840 chipset components are interconnected via an interface called ?hub interface?. the hub interface provides efficient communication between the chipset components. additional hardware platform features, supported by intel ? 840 chipset, include agp 4x, rdram, ultra dma/66, low pin count interface (lpc), and universal serial bus (usb). the intel ? 840 chipset architecture removes the requirement for the isa expansion bus that was traditionally integrated into the i/o subsystem of pcisets/agpsets. this eliminates many conflicts experienced when installing legacy isa hardware and drivers. the intel ? 840 chipset is also acpi compliant and supports full-on, stop grant, suspend to ram, suspend to disk, and soft-off power management states. through the use of an appropriate lan device, intel ? 840 chipset also supports wake-on-lan * for remote administration and troubleshooting.
14 datasheet figure 1. intel ? ? ? ? 840 chipset system block diagram main memory (2 gb max.) sys_blk 82840 memory controller hub (mch) agp 4x graphics controller hub interface a agp 2.0 processor processor 82806aa pci 64 hub (p64h) six 33 mhz pci slots or two 66 mhz pci slots 82801aa i/o controller hub (ich) fwh flash bios gpio 2 usb ports 4 ide drives ac'97 codec(s) (optional) ac'97 2.1 33 mhz pci bus pci slots pci agent lpc i/f super i/o rdram rdram channel a channel b memory interface (300 mhz, 400 mhz) hub interface b rdram 82803aa (mrh-r) rdram rdram 82803aa (mrh-r) rdram channel a channel b memory expansion card shaded blocks are intel ? 840 chipset components 82801aa i/o controller hub (ich) the ich is a highly integrated multifunctional i/o controller hub that provides the interface to the pci bus and integrates many of the functions needed in today?s pc platforms. the mch and ich communicate over a dedicated hub interface. functions and capabilities include: ? pci rev 2.2 compliant with support for 33 mhz pci operations ? supports up to 6 req/gnt pairs (pci slots) ? power management logic support ? enhanced dma controller, interrupt controller and timer functions ? integrated ide controller; ultra ata/66 ? usb host interface with support for 2 usb ports ? system management bus (smbus) compatible with most i 2 c devices ? ac?97 2.1 compliant link for audio and telephony codecs ? low pin count (lpc) interface ? fwh flash bios interface support ? alert on lan*
82840 mch r datasheet 15 82806aa pci 64 hub (p64h) the pci-64 hub(p64h) is a peripheral chip that performs pci bridging functions between the hub interface and the pci bus and is used as an integral part of the intel ? 840 chipset. the p64h has a 16-bit primary hub interface to the memory controller hub (mch) and a secondary 64-bit pci bus interface. the 64-bit interfaces inter-operates transparently with either 64-bit or 32-bit devices. the p64h is fully compliant with the pci local bus specification, revision 2.2 . the p64h functions include: ? pci hot plug controller ? integrated pci low skew clock driver ? i/o apic 82803aa memory repeater hub (mrh-r) the mrh-r supports multiple rdram channels from an ?expansion channel.? expansion channel is the interconnect between the mch and the mrh-r. each mrh-r can support up to 2 ?stick? channels. the mrh-r acts as a pass-through logic with fixed delay for read and write accesses from expansion channels to rdram channels. the mrh-r features include: ? maximum of 1 gb memory per channel ? nap entry/exit, power down exit, refresh and precharge on a channel upon request from memory controller ? core logic gating to minimize power consumption ? clock generation for direct rambus* clock generator (drcg) ? integrated smbus controller to read/write data from/to spd eeprom on the rimms
16 datasheet 1.2. 82840 mch overview the 82840 memory hub (mch) component provides the processor interface, dram interface, and agp interface in a 82840 workstation or server platform. it supports dual channels of direct rambus dram operating in lock-step. it also supports 4x agp data transfers and 2x/4x agp fast writes. the mch contains advanced power management logic. the intel 840 chipset platform uses the dedicated i/o controller hub (ich) designed for use with the mch to provide the features required by a workstation or a server platform. in addition, the 82840 mch implements a second 16 bit/66 mhz port that may be used to connect an advanced 64 bit pci interface (p64h). communication with ich and p64h is accomplished via a high speed interface called ?hub interface?. the 82840 mch contains the following functionality: ? supports up to two processor configurations at 100 mhz or 133 mhz ? gtl+ host bus supporting 32 or 36-bit host addressing ? dual direct rambus channels supported for 300 mhz or 400 mhz operation ? 4 gb support for rdram devices ? agp interface with 4x sba/data transfer and 2x/4x fast write capability ? 8 bit, 66 mhz hub interface a to ich ? 16 bit, 66 mhz hub interface b to p64h ? fully optimized data paths and buffering ? distributed arbitration for highly concurrent operation host interface the 82840 mch supports up to two processors at fsb frequencies of 100/133 mhz using agtl+ signaling. in a dual-processor system one of the two processor agent ids must be assigned to id0. the 82840 mch supports either 32 or 36-bit host addresses, allowing the processor to access the entire 4 gb of the mch?s memory address space. the mch has an 8-deep in-order queue to support up to eight outstanding pipelined address requests on the host bus. host-initiated i/o cycles are positively decoded to agp, hub interface b, or mch configuration space and subtractively decoded to hub interface a. host-initiated memory cycles are positively decoded to agp, hub interface b, or dram, and are again subtractively decoded to hub interface a. agp semantic memory accesses initiated from agp to dram are not snooped on the host bus. memory accesses initiated from agp using pci semantics and from either hub interface to dram will be snooped on the fsb. memory accesses whose addresses lie within the agp aperture are translated using the agp address translation table, regardless of the originating interface. the mch provides optional host bus error checking for data, address, request and response signals. single bit errors (correctable) are always corrected if it is enabled and can be configured to generate hub interface smi or sci cycles to ich on the host data bus. multiple bit errors (uncorrectable) can be configured to generate a berr# condition on the host bus. the mch can be configured to generate hub interface serr or sci cycles to ich for berr# or ierr# error conditions. the mch can also generate the hub interface serr cycle to ich for the host address parity or the request parity conditions. the mch also supports response parity rsp# for the response signals rs[2:0]#.
82840 mch r datasheet 17 dram interface the mch directly supports dual channels of direct rambus* memory operating in lock-step using rambus* signaling level (rsl) technology. only 300 mhz and 400 mhz direct rambus* devices are supported in any of 64, 128 or 256mb technology. the 64 and 128 mbit rdrams use page sizes of 1 kb, while 256mb devices target 1 kb or 2 kb pages. a maximum of 64 rambus* devices (64mb technology implies 512 mb maximum in 16 mb increments, 256mb technology implies 2 gb maximum in 64 mb increments) are supported on the paired channels without external logic. the mch also supports a single external rambus* channel repeater per connected channel. each repeater adds a single additional branch to the main channel, which yields a total of four rambus* channels. the following table shows the maximum dram array size and the minimum increment size for the various dram densities supported. table 1. maximum memory vs dram densities directly supported supported via repeater(s) rdram technology increments maximum increments maximum 64mb 16 mb 512 mb 16 mb 1 gb 128mb 32 mb 1 gb 32 mb 2 gb 256mb 64 mb 2 gb 64 mb 4 gb the 82840 mch provides optional ecc error checking for dram data integrity. during dram writes, ecc is generated on a qword (64 bit) basis. partial qword writes require a read-modify-write cycle when ecc is enabled. during dram reads, the mch supports detection of single-bit and multiple-bit errors, and correct single bit errors, when correction is enabled. the mch scrubs single bit errors by writing the corrected value back into dram for all reads, when hardware scrubbing is enabled (except for those launched to satisfy an agp aperture translation). ecc can only be enabled when all rdram devices populated in a system support the extra two data bits used to store the ecc code. the 82840 mch provides a maximum dram address decode space of 4 gb. the mch does not remap apic memory space in hardware. it is the bios or system designers responsibility to limit dram configuration so that adequate pci, agp, high bios, and apic memory space can be allocated. agp interface a single agp device or connector (not both) is supported by the mch agp interface. the agp buffers operate in one of two selectable modes to support the agp universal connector: ? 3.3v drive, not 5 volt safe: this mode is compliant to the agp 1.0 specification ? 1.5v drive, not 3.3 volt safe: this mode is compliant with the agp 2.0 specication the following table shows the agp data rate and the signaling levels supported by the mch. signaling level data rate 1.5v 3.3v 1x agp * yes yes 2x agp yes yes 4x agp yes no * note agp frame # data rate and signaling level is the same as 1x agp.
18 datasheet the agp interface supports 4x agp signaling and 4x fast writes. agp semantic (pipe# or sba[7:0]) cycles to dram are not snooped on the host bus. agp frame# cycles to dram are snooped on the host bus. the mch supports pipe# or sba[7:0] agp address mechanisms, but not both simultaneously. either the pipe# or the sba[7:0] mechanism must be selected during system initialization. high priority accesses are supported. only memory writes from either hub interface a or hub interface b to agp are allowed. no transactions from agp to the hub interface are allowed. mch clocking the mch has two clock input pins: cpuclk for the host clock and clk66 for the agp clock. clock synthesizer chip(s) are responsible for generating the host clocks, agp clocks, pci clocks, and rambus* clocks. these clocks must be synchronous to each other. the mch host interface runs at 100 mhz or 133 mhz. the supported speed bins for direct rdram devices are 300 mhz and 400 mhz. the agp interface runs at a constant 66 mhz. the hub interface interfaces run at the same base frequency as the agp interface. 1.3. terminology term description mch the 82840 memory controller hub component that contains the processor interface, dram controller, pci-64 bridge and agp interface. it communicates with the 82840 i/o controller hub (ich) and the 64 bit pci bus hub (p64h) over a private interconnect called ?hub interface?. ich the 82801aa io controller hub component that contains the primary pci interface, lpc interface, usb, ata-66, and other io functions. the ich communicates with the mch over a private interconnect called hub interface. p64h the 82806aa bus controller hub component that contains a 64-bit, 66 mhz pci interface. host this term is used synonymously with processor. core the internal base logic in the mch. hub interface the private interconnect that ties the mch to the ich and/or p64h. in this document hub interface cycles originating from or destined for the primary pci interface on the ich are generally referred to as hub interface a cycles. cycles originating from or destined for any target on the secondary hub interfaces are described as hub interface b cycles. accelerated graphics port (agp) the agp interface in the mch. the mch supports a subset of 3.3v, 66 mhz components, 3.3v 66/133 mhz agp 2.0 compliant components, and the new 1.5v 66/266 mhz components. pipe# and sba addressing cycles and their associated data phases are generally referred to as agp transactions. rsl rambus* signaling level is the name of the signaling technology used by rambus*.
82840 mch r datasheet 19 term description single channel-pair mode in this mode, the 82840 mch is configured to directly support rdram devices on its dual rambus* channel. there is no mrh-r used on the memory subsystem. multiple channel-pair mode in this mode, the 82840 mch is configured to use mrh-r on the memory subsystem. each rambus* channel of the mrh-r on the mch direct rambus* interface a matches with one rambus* channel of the mrh-r on the direct rambus* interface b. single device-pair in the single channel-pair mode, the 82840 mch is configured to directly support rdram devices on its dual rambus* channel. each rdram deivce of the mch direct rambus* interface a matches with one rdram device of the direct rambus* interface b. there is no mrh-r used on the memory subsystem. multiple device-pair in the multiple channel-pair mode, the 82840 mch is configured to use mrh-r on the memory subsystem. each rdram deivce on direct rambus* interface a matches with one rdram device on the direct rambus* interface b.
20 datasheet this page is left intentionally blank.
82840 mch r datasheet 21 2. signal description this section provides a detailed description of mch signals. the signals are arranged in functional groups according to their associated interface. the ?#? symbol at the end of a signal name indicates that the active, or asserted state occurs when the signal is at a low voltage level. when ?#? is not present after the signal name the signal is asserted when at the high voltage level. the following notations are used to describe the signal type: i input pin o output pin i/o bi-directional input/output pin s/t/s sustained tristate. this pin is driven to its inactive state prior to tri-stating. as/t/s active sustained tristate. this applies to some of the hub interface signals. this pin is weakly driven to its last driven value. the signal description also includes the type of buffer used for the particular signal: gtl+ open drain gtl+ interface signal. refer to the gtl+ i/o specification for complete details. agp agp interface signals. these signals can be programmed to be compatible with agp 2.0 3.3v or 1.5v signaling environment dc and ac specifications. in 3.3v mode the buffers are not 5v tolerant. in 1.5v mode the buffers are not 3.3v tolerant. cmos cmos buffers. rsl rambus* signaling level interface signal.
22 datasheet 2.1. host interface signals name type description ads# i/o gtl+ address strobe: the processor bus owner asserts ads# to indicate the first of two cycles of a request phase. ap[1:0]# i/o gtl+ address parity: ap[1:0]# provide parity over the address signals. ap1# covers ha[35:24]#; ap0 # covers ha[23:3]#. these signals must be valid for two clo cks beginning when ads# is asserted. berr# i/o gtl+ bus error: the berr# signal is asserted to indicate an unrecoverable error without a bus protocol violation. bnr# i/o gtl+ block next request: used to block the current request bus owner from issuing a new requests. this signal is used to dynamically control the processor bus pipeline depth. breq0# o gtl+ symmetric agent bus request: asserted by the mch when cpurst# is asserted to configure the symmetric bus agents. the breq0# is negated 2 host clo cks after cpurst# is negated. bpri# o gtl+ priority agent bus request: the mch is the only priority agent on the processor bus. it asserts this signal to obtain the ownership of the address bus. this signal has priority over symmetric bus requests and causes the current symmetric owner to stop issuing new transactions unless the hlock# signal was asserted. cpurst# o gtl+ cpu reset. the cpurst# pin is an output from the mch. the mch asserts cpurst# while rstin# (pcirst# from ich) is asserted for approximately 1 ms after rstin# is deasserted. the cpurst# allows the processors to begin execution in a known state. dbsy# i/o gtl+ data bus busy: used by the data bus owner to hold the data bus for transfers requiring more than one cycle. defer# o gtl+ defer: mch generates a deferred response as defined by the rules of the mch?s dynamic defer policy. the mch also uses the defer# signal to indicate a processor retry response. dep[7:0]# i/o gtl+ host ecc: the dep[7:0]# signals are driven during the data phase by the agent responsible for driving hd[63:0]#. the dep[7:0]# signals provide ecc protection for the signals on the data bus. drdy# i/o gtl+ data ready: asserted for each cycle that data is transferred. ha[35:3]# i/o gtl+ host address bus: ha[35:3]# connect to the processor address bus. during processor cycles, ha[35:3]# are inputs. the mch drives ha[35:3]# during snoop cycles on behalf of hub interface and agp frame# initiators. note that the address is inverted on the processor bus. hd[63:0]# i/o gtl+ host data: these signals are connected to the processor data bus. note that the data signals are inverted on the processor bus. hit# i/o gtl+ hit: indicates that a caching agent is retaining an unmodified version of the requested line. hit# is also driven in conjunction with hitm# by the target to extend the snoop window. hitm# i/o gtl+ hit modified: indicates that a caching agent holds a modified version of the requested line and that this agent assumes responsibility for providing the line. also, driven in conjunction with hit# to extend the snoop window.
82840 mch r datasheet 23 name type description hlock# i gtl+ host lock: all processor bus cycles sampled with the assertion of hlock# and ads#, until the negation of hlock# must be atomic (i.e., no hub interface or agp snoopable access to dram is allowed when hlock# is asserted by the processor). hreq[4:0]# i/o gtl+ host request command: asserted during both clocks of r equest phase. in the first clock, hreq[4:0]# define the transaction type to a level of detail that is sufficient to begin a snoop request. in the second clock, the signals carry additional information to define the complete transaction type. the transactions supported by the mch host bridge are defined in the functional description chapter. htrdy# o gtl+ host target ready: htrdy# indicates that the target of the processor transaction is able to enter the data transfer phase. ierr# i cmos internal error: a processor asserts ierr# when it detects an internal error unrelated to bus operation. rp# i/o gtl+ request parity: rp# provides parity protection over ads# and hreq[4:0]#. rp# must be valid for two clocks beginning when ads# is asserted. rs[2:0]# o gtl+ response signals: indicates type of response according to the following the table: rs[2:0] response type 000 idle state 001 retry response 010 deferred response 011 reserved (not driven by mch) 100 hard failure (not driven by mch) 101 no data response 110 implicit writeback 111 normal data response rsp# o gtl+ response parity: rsp# is always driven by the 82840 mch and must be valid on all clocks. res ponse parity is correct if there are an even number of low signals in the set consisting of the rs[2:0]# signals and the rsp# signal. the following is the list of processor bus interface signals that are not supported by mch. signal function not support by mch aerr# address parity error error phase response to parity error binit# bus initialization signal rest of the host bus state machines without full mch reset
24 datasheet 2.2. direct rambus* interface a signal type description cha_dqa[8:0] i/o rsl rambus data byte a (cha): bi-directional 9-bit data bus a on the rambus* interface a. data signals used for read and write operations on rambus* channel ?a?. cha_dqb[8:0] i/o rsl rambus data byte b (cha): bi-directional 9-bit data bus b on the rambus* interface a. data signals used for read and write operations on rambus* channel ?a?. cha_rq[7:5]/ cha_row[2:0] o rsl row access control (cha): three request package pins containing control and address information for row accesses. note that rq_a[7:5] can also be named as row_a[2:0] signals. cha_rq[4:0]/ cha_col[4:0] o rsl column access control (cha): five request package pins containing control and address information for column accesses. note that rq_a[4:0] can also be named as col_a[4:0] signals. cha_ctm i rsl clock to master (cha): one of the two differential transmit clock signals used for rdram operations on rambus* channel ?a?. it is an input to the mch and is generated from an external clock synthesizer. cha_ctm# i rsl clock to master compliment (cha): one of the two differential transmit clock signals used for rdram operations on rambus* channel ?a?. it is an input to the mch and is generated from an external clock synthesizer. cha_cfm o rsl clock from master (cha): one of the two differential receive clock signals used for rdram operations on rambus* channel ?a?. it is an output from the mch. cha_cfm# o rsl clock from master compliment(cha): one of the two differential receive clock signals used for rdram operations on rambus* channel ?a?. it is an output from the mch. cha_exp[1:0] o rsl expansion (cha): these signals are used to communicate to an external rambus* repeater on rambus* channel ?a?. the repeater increases the maximum memory size supported by the mch. cha_cmd o cmos command (cha): command output to the rambus* devices used for power mode control, configuring the sio daisy chain, and framing sio operations. cha_sck o cmos serial clock (cha): this signal provides clocking for register accesses and selects rambus* channel ?a? devices for power management. cha_sio i/o cmos serial input/output (a): bi-directional serial data signal used for device initialization, register operations, power mode control, and device reset.
82840 mch r datasheet 25 2.3. direct rambus* interface b signal name type description chb_dqa[8:0] i/o rsl rambus data byte a (chb): bi-directional 9-bit data bus a on the rambus* interface b. data signals used for read and write operations on rambus* channel ?a?. chb_dqb[8:0] i/o rsl rambus data byte b (chb): bi-directional 9-bit data bus b on the rambus* interface b. data signals used for read and write operations on rambus* channel ?a?. chb_rq[7:50]/ chb_row[2:0] o rsl row access controlrequest control (chb): three request package pins containing control and address information for row accesses. note that chb_rq[7:5] can also be named as chb_row[2:0] signals. chb_rq[4:0]/ chb_col[4:0] o rsl column access control (chb): five request package pins containing control and address information for column accesses. note that chb_rq[4:0] can also be named as chb_col[4:0] signals. chb_ctm i rsl clock to master (chb): one of the two differential transmit clock signals used for rdram operations on rambus* channel ?b?. chb_ctm is an input to the mch and is generated from an external clock synthesizer. chb_ctm# i rsl clock to master compliment (chb): one of the two differential transmit clock signals used for rdram operations on rambus* channel ?b?. chb_ctm# is an input to the mch and is generated from an external clock synthesizer. chb_cfm o rsl clock from master (chb): one of the two differential receive clock signals used for rdram operations on rambus* channel ?b?. chb_cfm is an output from the mch. chb_cfm# o rsl clock from master compliment (chb): one of the two differential receive clock signals used for rdram operations on rambus* channel ?b?. chb_cfm# is an output from the mch. chb_exp[1:0] o rsl expansion (chb): these signals are used to communicate to an external rambus* repeater on rambus* channel ?b?. the repeater increases the maximum memory size supported by the mch. chb_cmd o cmos command (chb): command output to the rambus* devices used for power mode control, configuring the sio daisy chain, and framing sio operations. chb_sck o cmos serial clock (chb): this signal provides clocking for register accesses and selects rambus* channel ?b? devices for power management. chb_sio i/o cmos serial input/output (chb): serial input/output a: bi-directional serial data signal used for device initialization, register operations, power mode control, and device reset.
26 datasheet 2.4. hub interface a signals name type description hla_stb i/o cmos hub interface a strobe. one of two differential strobe signals used to transmit or receive packet data over hub interface a. hla_stb# i/o cmos hub interface a strobe compliment. one of two differential strobe signals used to transmit or receive packet data over hub interface a. hla[11:0] i/o cmos hub interface a signals: signals used for the hub interface. hlazcomp i/o cmos impedance compensation for hub interface a: this signal is used to calibrate the hub interface a i/o buffers. this signal pin must be connected to a pcb trace representative of the hub interface a data signal traces but sufficiently long to present a long shelf before signal reflection occurs. the hub interface a buffers are calibrated based on the measured shelf voltage. 2.5. hub interface b signals name type description hlb_stb[1:0] i/o cmos hub interface b strobe: one of two differential strobe signals used to transmit or receive packet data over hub interface b. hlb_stb[1:0]# i/o cmos hub interface b strobe compliment: one of two differential strobe signals used to transmit or receive packet data over hub interface b. hlb[19:0] i/o cmos hub interface b signals: signals used for the hub interface. hlbrcomp i/o cmos resistor compensation for hub interface b: hlbrcomp is used to calibrate the hub interface b i/o buffers. this signal pin must be connected to an external resistor to ground with the value z0/2. z0 is the pcb trace impedance used on the hub interface b. 2.6. agp interface signals for more details on the operation of these signals, refer to the agp interface specification, revision 2.0 . 2.6.1. agp addressing signals there are two mechanisms the agp master can use to enqueue agp requests: pipe# and sba (side- band addressing). upon initialization, one of the methods is chosen. the master may not switch methods without a full reset of the system. when pipe# is used to enqueue addresses, the master is not allowed to queue addresses using the sba bus. for example, during configuration time, if the master indicates that it can use either mechanism, the configuration software will indicate which mechanism the master will use. once this choice has been made, the master continues to use the mechanism selected until the system is reset (and reprogrammed) to use the other mode. this change of modes is not a dynamic mechanism but rather a static decision when the device is first being configured after reset.
82840 mch r datasheet 27 name type description pipe# i agp pipeline: pipe# operation: this signal is asserted by the agp master to indicate a full-width adress is to be enqueued on by the target using the ad bus. one address is placed in the agp request queue on each rising clock edge while pipe# is asserted. sba operation: this signal is not used if sba (side band addressing) is selected. frame# operation: this signal is not used during agp frame# operation. sba[7:0] i agp side-band addressing: pipe# operation: these signals are not used during pipe# operation. sba operation: these signals (the sba, or side-band addressing, bus) are used by the agp master (graphics component) to place addresses into the agp request queue. the sba bus and ad bus operate independently. that is, transaction can proceed on the sba bus and the ad bus simultaneously. frame# operation: these signals are not used during agp frame# operation. 2.6.2. agp flow control signals name type description rbf# i agp receive buffer full: pipe# and sba operation: read buffer full indicates if the master is ready to accept previously requested low priority read data. when rbf# is asserted, the mch is not allowed to initiate the return low priority read data. thus, the mch can finish returning the data for the request currently being serviced; however, it can not begin returning data for the next request. rbf# is only sampled at the beginning of a cycle. if the agp master is always ready to accept return read data, it is not required to implement this signal. frame# operation: this signal is not used during agp frame# operation. wbf# i agp write-buffer full: pipe# and sba operation: write bufffer full indicates if the master is ready to accept fast write data from the mch. when wbf# is asserted, the mch is not allowed to drive fast write data to the agp master. wbf # is only sampled at the beginning of a cycle. if the agp master is always ready to accept fast write data, it is not required to implement this signal. frame# operation: this signal is not used during agp frame# operation.
28 datasheet 2.6.3. agp status signals name type description st[2:0] o agp status bus: pipe# and sba operation: these signals provide information from the arbiter to a agp master on what it may do. st[2:0] only have meaning to the master when its gnt# is asserted. when gnt# is deasserted, these signals have no meaning and must be ignored. refer to the agp interface specificaiton, revision 2.0 for further explanation of the st[2:0] values and their meanings. frame# operation: these signals are not used during frame# based operation; except that a ?111? indicates that the master may begin a frame# transaction. an external 8.2 k ? pullup to vddq is required on each st[2:0] signal, except st0. an external 1 k ? pulldown is needed on st0 for enabling host bus ecc generation. 2.6.4. agp clocking signals?strobes name type description ad_stb0 i/o s/t/s agp ad bus strobe-0: 1x operation: this signal is not used during 1x operation. 2x operation: during 2x operation, this signal provides timing for the ad[15:0] and c/be[1:0]# signals. the agent that is providing the data will drive this signal. 4x operation: during 4x operation, this is one-half of a differential strobe pair that provides timing information for the ad[15:0] and c/be[1:0]# signals. ad_stb0# i/o s/t/s agp ad bus strobe-0 compliment: 1x operation: this signal is not used during 1x operation. 2x operation: during 2x operation, this signal is not used. 4x operation: during 4x operation, this is one-half of a differential strobe pair that provides timing information for the ad[15:0] and c/be[1:0]# signals. the agent that is providing the data will drive this signal. ad_stb1 i/o s/t/s agp ad bus strobe-1: 1x operation: this signal is not used during 1x operation. 2x operation: during 2x operation, this signal provides timing for the ad[31:16] and c/be[3:2]# signals. the agent that is providing the data will drive this signal. 4x operation: during 4x operation, this is one-half of a differential strobe pair that provides timing information for the ad[31:16] and c/be[3:2]# signals. the agent that is providing the data will drive this signal. ad_stb1# i/o s/t/s agp ad bus strobe-1 compliment: 1x operation: this signal is not used during 1x operation. 2x operation: during 2x operation, this signal is not used. 4x operation: during 4x operation, this is one-half of a differential strobe pair that provides timing information for the ad[16:31] and c/be[2:3]# signals. the agent that is providing the data will drive this signal.
82840 mch r datasheet 29 name type description sb_stb i agp sba bus strobe: 1x operation: this signal is not used during 1x operation. 2x operation: during 2x operation, this signal provides timing for the sba bus signals. the agent that is driving the sba bus will drive this signal. 4x operation: during 4x operation, this is one-half of a differential strobe pair that provides timing information for the sba bus signals. the agent that is driving the sba bus will drive this signal. sb_stb# i agp sba bus strobe compliment: 1x operation: this signal is not used during 1x operation. 2x operation: during 2x operation, this signal is not used. 4x operation: during 4x operation, this is one-half of a differential strobe pair that provides timing information for the sba bus signals. the agent that is driving the sba bus will drive this signal. 2.6.5. agp frame# signals for transactions on the agp interface carried using agp frame# protocol, these signals operate similar to their semantics in the pci 2.1 specification. the exact role of all agp frame# signals are defined below. name type description g_frame# i/o s/t/s agp frame: pipe# and sba operation: not used by agp sba and pipe#, but used during agp frame# . fast write operation: g_frame# is used to frame transactions as an output from the mch during fast writes. frame# operation: g_frame# is an output when the mch acts as an initiator on the agp interface. g_frame# is asserted by the mch to indicate the beginning and duration of an access. g_frame# is an input when the mch acts as a frame# based agp target. as a frame# based agp target, the mch latches the c/be[3:0]# and the ad[31:0] signals on the first clock edge on which it samples frame# active. g_irdy# i/o s/t/s agp initiator ready: pipe# and sba operation: not used while enqueueing requests via agp sba and pipe#, but used during the data phase of pipe# and sba transactions. frame# operation: g_irdy# is an output when mch acts as a frame# based agp initiator and an input when the mch acts as a frame# based agp target. the assertion of g_irdy# indicates the current frame# based agp bus initiator's ability to complete the current data phase of the transaction. fast write operation: g_irdy# indicates the agp compliant master is ready to provide all write data for the current transaction. once g_irdy# is asserted for a write operation, the master is not allowed to insert wait states. the master is never allowed to insert a wait state during the initial data transfer (32 bytes) of a write transaction. however, it may insert wait states after each 32 byte block is transferred.
30 datasheet name type description g_trdy# i/o s/t/s agp target ready: pipe# and sba operation: not used while enqueueing requests via agp sba and pipe#, but used during the data phase of pipe# and sba transactions. frame# operation: g_trdy# is an input when the mch acts as an agp initiator and an output when the mch acts as a frame# based agp target. the assertion of g_trdy# indicates the target?s ability to complete the current data phase of the transaction. fast write operation: g_trdy# indicates the agp compliant target is ready to receive write data for the entire transaction (when the transfer size is less than or equal to 32 bytes) or is ready to transfer the initial or subsequent block (32 bytes) of data when the transfer size is greater than 32 bytes. the target is allowed to insert wait states after each block (32 bytes) is transferred on write transactions. g_stop# i/o s/t/s agp stop: pipe# and sba operation: this signal is not used during pipe# or sba operation. frame# operation: stop# is an input when the mch acts as a frame# based agp initiator and an output when the mch acts as a frame# based agp target. stop# is used for disconnect, retry, and abort sequences on the agp interface. g_devsel# i/o s/t/s agp device select: pipe# and sba operation: this signal is not used during pipe# or sba operation. frame# operation: devsel#, when asserted, indicates that a frame# based agp target device has decoded its address as the target of the current access. the mch asserts devsel# based on the dram address range being accessed by a pci initiator. as an input it indicates whether any device on the bus has been selected. fast write operation: g_devsel# is used when the transaction cannot complete during the block data transfer g_req# i agp request: sba operation: this signal is not used during pipe# or sba operation. pipe# and frame# operation: req#, when asserted, indicates that a frame# or pipe# based agp master is requesting use of the agp interface. this signal is an input into the mch. g_gnt# o agp grant: sba, pipe# and frame# operation: gnt# along with the information on the st[2:0] signals (status bus) indicates how the agp interface will be used next. refer to the agp interface specificaiton , revision 2.0 for further explanation of the st[2:0] values and their meanings. g_ad[31:0] i/o agp address/data bus: pipe# and frame# operation: ad[31:0] are used to transfer both address and data information on the agp inteface. sba operation: ad[31:0] are used to transfer data on the agp interface.
82840 mch r datasheet 31 name type description g_c/be[3:0]# i/o agp command/byte enable: frame# operation: during the address phase of a transaction, c/be[3:0]# define the bus command. during the data phase, c/be[3:0]# are used as byte enables. the byte enables determine which byte lanes carry meaningful data. the commands issued on the c/bex# signals during frame# based agp are the same c/bex# command described in the pci 2.1 specification. pipe# operation: when an address is enqueued using pipe#, the c/bex# signals carry command information. refer to the agp 2.0 interface specification revision 2.0 for the definition of these commands. the command encoding used during pipe# based agp is different than the command encoding used during frame# based agp cycles (or standard pci cycles on a pci bus). sba operation: these signals are not used during sba operation. g_par i/o agp parity: frame# operation: g_par is driven by the mch when it acts as a frame# based agp initiator during address and data phases for a write cycle, and during the address phase for a read cycle. par is driven by the mch when it acts as a frame# based agp target during each data phase of a frame# based agp memory read cycle. even parity is generated across ad[31:0] and c/be[3:0]#. sba and pipe# operation: this signal is not used during sba and pipe# operation. g_serr# i agp system error: g_serr# can be pulsed to report a system error condition. upon sampling g_serr# active, the mch can generate a hub interface serr cycle to the ich. notes: 1. pcirst# from the ich is connected to rstin# and is used to reset agp interface logic within the mch. the agp agent will also use pcirst# provided by the ich as an input to reset its internal logic. 2. the lock# signal is not supported on the agp interface, even for frame based agp operations. 3. the perr# signal is not supported on the agp interface. 2.7. clocks, reset, and miscellaneous name type description cpuclk i cmos host clock in: cpuclk receives a buffered host clock from the external clock synthesizer. this clock is used by all of the mch logic that is in the host clock domain. note that the clock synthesizer drives this signal to 2.5v. clk66 i cmos 66mhz clock in: . clk66 receives a buffered clock from the clock synthesizer that is synchronously derived from the host clock. this clock is used by all of the mch logic that is in the agp clock domain. note that the clock synthesizer drives this signal to 3.3v, and this input is 3.3v tolerant. rclkout[a,b] o cmos rambus clock out: rclkout[a,b] provide divided down versions of the rambus* clock as feedback to the rambus* clock synthesizers for phase alignment. note that this pin will only be driven to 1.8v. hclkout[a,b] o cmos host clock out: hclkout[a,b] provide divided down versions of the host clock as feedback to the rambus* clock synthesizers for phase alignment. note that this pin will only be driven to 1.8v.
32 datasheet name type description rstin# i cmos reset in: when asserted, rstin# asynchronously resets the mch logic. this signal is connected to the pcirst# output of the ich. all agp output and bi- directional signals will also tri-state compliant to pci rev 2.0 and 2.1 specifications. note that this input needs to be 3.3v tolerant. test# i cmos test input: this pin is used for manufacturing and board level test purposes. overt# i cmos overtemperature condition: an active low input signal generated by external hardware to indicated the overtemperature condition in the memory subsystem. 2.8. voltage references, pll power signal name description gtlref[a:b] gtl reference: reference voltage input for the host gtl interface. agprcomp agp rcomp: agprcomp is used to calibrate agp gtl i/o buffers. this signal must be connected to a pcb trace representative of the agp bus data signal traces but sufficiently long to present a long shelf before signal reflection occurs. the agp buffers are calibrated based on the measured shelf voltage. cha_ref[1:0] rambus channel a reference: reference voltage input for the rambus* channel a rsl interface. chb_ref[1:0] rambus channel b reference: reference voltage input for the rambus* channel b rsl interface. agpref agp reference: reference voltage input for the agp interface. hlaref hub interface a reference: refererence voltage input for the hub interface. hlbref hub interface b reference: refererence voltage input for the hub interface. vcc1_8 1.8v power supply: the 1.8v power input pin vddq agp i/o power supply: the power supply input for the agp i/o supply. vtt agtl+ 1.5v volatage: the gtl+ bus 1.5v termination voltage inputs. vss ground:
82840 mch r datasheet 33 2.9. strap signals this section provides the strap options invoked by various mch signal pins. name definition hla10 host bus frequency: this signal is latched on the rising edge of rstin#. it indicates what the host fsb frequency is to select the correct internal frequency ratios. this value can be read from the mchcfg register. there is no internal pullup or pulldown resistor. hla10 host bus frequency 0 100 mhz 1 133 mhz ha7# cpu bus in-order queue depth: the value on ha7# is sampled by all host bus agents (including the mch) on the rising edge of cpurst#. it?s latched value determines the maximum ioq depth mode supported on the host bus. if ha7# is sampled low the ioq depth on the bus is one. if ha7# is sampled high, the ioq depth on the bus is the maximum of eight. when the ioq depth on the bus is set to 8, the mch does not limit the number of queued transactions, since it supports an ioq depth of 8. the mch does not drive ha7# during cpurst#. if an ioq depth of 1 is desired, ha7# needs to be driven low during cpurst# by external logic. st0 host bus ecc generation: st0 is latched on the rising edge of rstin#. it is used to enable the data ecc protection covering hd[63:0]#. this value can be read from the herrctl register. there is no internal pullup or pulldown resistor. to strap for host bus ecc enabled, a 1 k ? pulldown should be connected to st0. st0 should have a 8.2 k ? external pullup resistor to vddq to disable the hot bus ecc generation. st0 ecc generation on dep[7:0]# 0 enable (external 1 k ? pulldown) 1 disable (external 8.2 k ? pullup))
34 datasheet this page is left intentionally blank.
82840 mch r datasheet 35 3. register description this chapter describes the mch pci configuration registers. a detailed bit description is provided. the mch contains two sets of software accessible registers, accessed via the host i/o address space: ? control registers i/o mapped into the host i/o space, which control access to pci and agp configuration space (see section entitled i/o mapped registers) ? internal configuration registers residing within the mch are partitioned into two logical device register sets (?logical? since they reside within a single physical device). the first register set is dedicated to host-hub interface bridge/dram controller functionality (controls pci_a i.e. dram configuration, other chip-set operating parameters and optional features). the second register block is dedicated to host-agp bridge functions (controls agp interface configurations and operating parameters). the mch supports pci configuration space accesses using the mechanism denoted as configuration mechanism #1 in the pci specification. the mch internal registers (both i/o mapped and configuration registers) are accessible by the host. the registers can be accessed as byte, word (16-bit), or dword (32-bit) quantities, with the exception of conf_addr which can only be accessed as a dword. all multi-byte numeric fields use "little-endian" ordering (i.e., lower addresses contain the least significant parts of the field). 3.1. register nomenclature and access attributes symbol description ro read only. if a register is read only, writes to this register have no effect. r/w read/write. a register with this attribute can be read and written r/w/l read/write/lock. a register with this attribute can be read, written, and lock. r/wc read/write clear. a register bit with this attribute can be read and written. however, a write of a 1 clears (sets to 0) the corresponding bit and a write of a 0 has no effect. r/wo read/write once. a register bit with this attribute can be written to only once after power up. after the first write, the bit becomes read only. l lock. a register bit with this attribute becomes read only after a lock bit is set. reserved bits software must deal correctly with fields that are reserved. on reads, software must use appropriate masks to extract the defined bits and not rely on reserved bits being any particular value. on writes, software must ensure that the values of reserved bit positions are preserved. that is, the values of reserved bit positions must first be read, merged with the new values for other bit positions and then written back. note that software does not need to perform read, merge, write operation for the configuration address register.
36 datasheet symbol description reserved registers in addition to reserved bits within a register, the mch contains address locations in the configuration space of the host-hub interface a bridge/dram controller, host-agp bridge and host-hub interface b bridge entities that are marked ?reserved?. when a ?reserved? register location is read, a random value can be returned. (?reserved? registers can be 8-, 16-, or 32-bit in size). registers that are marked ?reserved? must not be modified by system software. writes to ?reserved? registers may cause system failure. default value upon reset upon a full reset, the mch sets all of its internal configuration registers to predetermined default states. upon a partial reset some of the mch configuration register bits associated with dram configuration are not reset. these register bits are identified in the bit descriptions below. some register values at reset are determined by external strapping options. the default state represents the minimum functionality feature set required to successfully bring up the system. hence, it does not represent the optimal system configuration. it is the responsibility of the system initialization software (usually bios) to properly determine the dram configurations, operating parameters and optional system features that are applicable, and to program the mch registers accordingly. 3.2. pci configuration space access the mch and the ich are physically connected by hub interface a. from a configuration standpoint, hub interface a is logically pci bus #0. as a result, all devices internal to the mch and ich appear to be on pci bus #0. the system?s primary pci expansion bus is physically attached to the ich and, from a configuration perspective, appears to be a hierarchical pci bus behind a pci-to-pci bridge and, therefore, has a programmable pci bus number. note: the primary pci bus is referred to as pci_a in this document and is not pci bus #0 from a configuration standpoint. the secondary hub interface port appears to system software to be a real pci bus behind a pci-to-pci bridge resident as device 2 on pci bus #0. the mch contains three pci devices within a single physical component. the configuration registers for devices 0, 1, and 2 are mapped as devices residing on pci bus #0. ? device 0: host-hub interface a bridge/dram controller. logically this appears as a pci device residing on pci bus #0. physically device 0 contains the standard pci registers, dram registers, the graphics aperture controller, and other mch specific registers. ? device 1: host-agp bridge. logically this appears as a ?virtual? pci-to-pci bridge residing on pci bus #0. physically device 1 contains the standard pci-to-pci bridge registers and the standard agp configuration registers (including the agp i/o and memory address mapping). ? device 2 host-hub interface b bridge. logically this bridge appears to be a pci-to-pci bridge device residing on pci bus #0. physically, device 2 contains the standard pci-to-pci registers. note: a physical pci bus #0 does not exist. the hub interface and the internal devices in the mch and ich logically constitute pci bus #0 to configuration software.
82840 mch r datasheet 37 pci bus configuration mechanism the pci bus defines a slot based "configuration space" that allows each device to contain up to 8 functions, with each function containing up to 256 8-bit configuration registers. the pci specification defines two bus cycles to access the pci configuration space: configuration read and configuration write. memory and i/o spaces are supported directly by the processor. configuration space is supported by a mapping mechanism implemented within the mch. the pci specification defines two mechanisms to access configuration space, mechanism #1 and mechanism #2. the mch supports only mechanism #1. the configuration access mechanism makes use of the conf_addr register and conf_data register. to reference a configuration register a dword i/o write cycle is used to place a value into conf_addr that specifies: ? the pci bus ? the device on that bus ? the function within the device ? a specific configuration register of the device function being accessed. conf_addr[31] must be 1 to enable a configuration cycle. conf_data then becomes a window into the four bytes of configuration space specified by the contents of conf_addr. any read or write to conf_data will result in the mch translating the conf_addr into the appropriate configuration cycle. the mch is responsible for translating and routing the processor i/o accesses to the conf_addr and conf_data registers to internal mch configuration registers, the hub interfaces or agp. routing configuration accesses to primary pci (pci_a), or agp the mch supports three bus interfaces: hub interface a, hub interface b, and agp. pci configuration cycles are selectively routed to one of these interfaces. the mch is responsible for routing pci configuration cycles to the proper interface. pci configuration cycles to ich internal devices and pci_a (including downstream devices) are routed to the ich via the hub interface a. agp configuration cycles are routed to agp. pci configuration cycles to p64h are routed to hub interface b. the agp interface is treated as a separate pci bus from the configuration point of view. routing of configuration accesses to both hub interface b and agp is controlled via the standard pci-pci bridge mechanism using information contained within the primary bus number, the secondary bus number, and the subordinate bus number registers of the host-agp internal ?virtual? pci-pci bridge device.
38 datasheet logical pci bus #0 configuration mechanism the mch decodes the bus number (bits 23:16) and the device number fields of the conf_addr register. if the bus number field of conf_addr is 0 the configuration cycle is targeting a pci bus #0 device. ? the host-hub interface a bridge/dram controller entity within the mch is hardwired as device 0 on pci bus #0. ? the host-agp bridge entity within the mch is hardwired as device 1 on pci bus #0. ? the host-hub interface b bridge entity within the mch is hardwired as device 2 on pci bus #0. configuration cycles to the mch internal devices are confined to the mch and not sent over the hub interface. accesses to devices #3 to #31 will be forwarded over the hub interface a. primary pci (pci_a) and downstream configuration mechanism if the bus number in the conf_addr is non-zero, and is less than the value programmed into both of the mch?s device 1 and device 2 secondary bus number register or greater than the value programmed into the subordinate bus number register, the mch will generate a type 1 configuration cycle over hub interface a. the ich compares the non-zero bus number with the secondary bus number and subordinate bus number registers of its p2p bridges to determine if the configuration cycle is meant for primary pci (pci_a), or a downstream pci bus. agp bus configuration mechanism from the chipset configuration perspective, agp is seen as another pci bus interface residing on a secondary bus side of the ?virtual? pci-pci bridge referred to as the mch host-agp bridge. on the primary bus side, the ?virtual? pci-pci bridge is attached to pci bus #0. therefore the primary bus number register is hardwired to ?0?. the ?virtual? pci-pci bridge entity converts type #1 pci bus configuration cycles on pci bus #0 into type 0 or type 1 configuration cycles on the agp interface. type 1 configuration cycles on pci bus #0 that have a bus number that matches the secondary bus number of the mch host-agp bridge will be translated into type 0 configuration cycles on the agp interface. if the bus number is non-zero, greater than the value programmed into the secondary bus number register, and less than or equal to the value programmed into the subordinate bus number register, the mch will generate a type 1 pci configuration cycle on agp.
82840 mch r datasheet 39 3.3. i/o mapped registers the mch contains a set of registers that reside in the host i/o address space ? the configuration address (conf_addr) register and the configuration data (conf_data) register. the configuration address register enables/disables the configuration space and determines what portion of configuration space is visible through the configuration data window. 3.3.1. conf_addr ? ? ? ? configuration address register i/o address: 0cf8h accessed as a dword default value: 00000000h access: read/write size: 32 bits conf_addr is a 32 bit register accessed only when referenced as a dword. a byte or word reference will "pass through" the configuration address register and the hub interface onto the pci0 bus as an i/o cycle. the conf_addr register contains the bus number, device number, function number, and register number for which a subsequent configuration access is intended. bit descriptions 31 configuration enable (cfge): this bit controls access to pci space. 1 = enable. 0 = disable. 30:24 reserved (these bits are read only and have a value of 0). 23:16 bus number: when the bus number is programmed to 00h, the target of the pci configuration cycle is a hub interface agent (mch, ich, etc.). the configuration cycle is forwarded to hub interface a if the bus number is programmed to 00h and the mch is not the target (the device number is 3). if the bus number is non-zero and matches the value programmed into the secondary bus number register of device 1, a type 0 pci configuration cycle will be generated on agp. if the bus number is non-zero, greater than the value in the secondary bus number register of device 1, and less than or equal to the value programmed into the subordinate bus number register of device 1, a type 1 pci configuration cycle will be generated on agp. if the bus number is non-zero and matches the value programmed into the secondary bus number register of device 2, a type 0 pci configuration cycle will be generated on hub interface b. if the bus number is non-zero, greater than the value in the secondary bus number register of device 2, and less than or equal to the value programmed into the subordinate bus number register of device 2, a type 1 pci configuration cycle will be generated on hub interface b. if the bus number is non-zero and does not fall within the ranges enumerated by device 1 and device 2?s secondary bus number or subordinate bus number register, a hub interface a configuration cycle is generated.
40 datasheet bit descriptions 15:11 device number: this field selects one agent on the pci bus selected by the bus number. when the bus number field is ?00?, the mch decodes the device number field. the mch is always device number 0 for the host-hub interface a bridge entity, device number 1 for the host-agp entity, and device number 2 for the host-hub interface b entity. therefore, when the bus number =0 and the device number=0, 1, or 2 the internal mch devices are selected. note that ad11, ad12, and ad13 must not be connected to any other pci_a bus device as idsel signals. if the bus number is non-zero and matches the value programmed into the secondary bus number register, a type 0 pci configuration cycle will be generated on agp. the mch decodes the device number field [15:11] and asserts the appropriate gad signal as an idsel. for pci-to-pci bridge translation, one of 16 idsels are generated. when bit [15] = 0, bits [14:11] are decoded to assert a single ad[31:16] idsel. gad16 is asserted to access device 0, gad17 for device 1, and so forth up to device 16 which asserts ad31. all device numbers higher than 16 cause a type 0 configuration access with no idsel asserted, which results in a master abort reported in the mch?s ?virtual? pci- pci bridge registers. for bus numbers resulting in hub interface a or hub interface b configuration cycles, the mch propagates the device number field as a[15:11]. 10:8 function number: this field is mapped to gad[10:8] during agp configuration cycles and a[10:8] during hub interface a or hub interface b configuration cycles. this allows the configuration registers of a particular function in a multi-function device to be accessed. the mch ignores configuration cycles to it?s two internal devices if the function number is not equal to 0. 7:2 register number: this field selects one register within a particular bus, device, and function as specified by the other fields in the configuration address register. this field is mapped to gad[7:2] during agp configuration cycles and a[7:2] during hub interface a or hub interface b configuration cycles. 1:0 reserved. 3.3.2. conf_data?configuration data register i/o address: 0cfch default value: 00000000h access: read/write size: 32 bits conf_data is a 32 bit read/write window into configuration space. the portion of configuration space that is referenced by conf_data is determined by the contents of conf_addr. bit descriptions 31:0 configuration data window (cdw): if bit 31 of conf_addr is 1, any i/o access to the conf_data register will be mapped to configuration space using the contents of conf_addr.
82840 mch r datasheet 41 3.4. host-hub interface a bridge/dram controller device registers (device 0) an ?s? in the default value field means that the power-up default value for that bit is determined by a strap. table 2. mch configuration space (device 0) address offset symbol register name default access 00?01h vid vendor identification 8086h ro 02?03h did device identification 1a21h ro 04?05h pcicmd pci command 0006h r/w 06?07h pcists pci status 0090h/0080h ro, r/wc 08h rid revision identification 00h ro 0ah subc sub-class code 00h ro 0bh bcc base class code 06h ro 0dh mlt master latency timer 00h r/w 0eh hdr header type 00h r/w 10?13h apbase aperture base configuration 00000008h r/w 2c?2dh svid subsystem vendor identification 0000h r/wo 2e?2fh sid subsystem identification 0000h r/wo 34h capptr capabilities pointer a0h / 00h ro 40?4fh gar[0:15] rdram group architecture register [15:0] 80h r/w 50?51h mchcfg mch configuration 00ss00000000 0s00b r/wo,r/w 52?57h ? reserved ? ? 58h fdhc fixed dram hole control 00h r/w 59?5fh pam[0:6] programmable attribute map [0:6] 00h r/w 60?61h gba0 rdram group boundary address 0 0001h r/w 62?63h gba1 rdram group boundary address 1 0001h r/w 64?65h gba2 rdram group boundary address 2 0001h r/w 66?67h gba3 rdram group boundary address 3 0001h r/w 68?69h gba4 rdram group boundary address 4 0001h r/w 6a?6bh gba5 rdram group boundary address 5 0001h r/w 6c-6dh gba6 rdram group boundary address 6 0001h r/w 6e?6fh gba7 rdram group boundary address 7 0001h r/w 70?71h gba8 rdram group boundary address 8 0001h r/w 72?73h gba9 rdram group boundary address 9 0001h r/w
42 datasheet address offset symbol register name default access 74?75h gba10 rdram group boundary address a 0001h r/w 76?77h gba11 rdram group boundary address b 0001h r/w 78?79h gba12 rdram group boundary address c 0001h r/w 7a?7bh gba13 rdram group boundary address d 0001h r/w 7c?7dh gba14 rdram group boundary address e 0001h r/w 7e?7fh gba15 rdram group boundary address f 0001h r/w 80?87h ? reserved ? ? 88h rdps rdram pool sizing register 10h r/w 89?8fh ? reserved ? ? 90?93h drd rdram device register data 0000h r/w 94?97h 94?96h ricm or ? rdram initialization control management reserved 0000_0000h ? r/w ? 98?9ch ? reserved ? ? 9dh smram system management ram control 02h r/w 9eh esmramc extended system management ram control 38h r/w 9fh ? reserved ? ? a0?a3h acapid agp capability identifier 00200002h /00000000h ro a4?a7h agpstat agp status register 1f000217h ro a8?abh agpcmd agp command register 00000000h rw ac?afh ? reserved ? ? b0?b3h agpctrl agp control register 00000000h r/w b4h apsize aperture size 00h r/w b5?b7h ? reserved ? ? b8?bbh attbase aperture translation table 00000000h r/w bch amtt agp mtt control register 00h r/w bdh lptt agp low priority transaction timer reg. 00h r/w beh rdt rdram timing 00h r/w bfh dramrc rdram refresh control 00h r/w c0?c3h ? reserved ? ? c4?c5h tom top of low memory 0000h r/w c6?c7h ? reserved 0000h ? c8?c9h errsts error status register 0000h r/wc ca?cbh errcmd error command register 0000h r/w cc?cdh smicmd smi command register 0000h r/w ce?cfh scicmd sci command register 0000h r/w
82840 mch r datasheet 43 address offset symbol register name default access d0?ddh ? reserved ? ? de?dfh skpd scratchpad data 0000h r/w e0?e1h herrctl_sts host error control/status 0000h r/w, r/wc e2?e3h derrctl_sts dram error control/status 0000h r/w,r/wc e4?e7h eap error address pointer 0000h r/w e8?ebh agpbctrl agp buffer strength control 0000h r/w ec?f5h ? reserved ? ? f6 agpappend agp append disable 00h r/w f7 gtlnclamp gtl n clamp disable 00h r/w f8?ffh ? reserved ? ?
44 datasheet 3.4.1. vid?vendor identification register (device 0) address offset: 00?01h default value: 8086h attribute: read only size: 16 bits the vid register contains the vendor identification number. this 16-bit register combined with the device identification register uniquely identify any pci device. writes to this register have no effect. bit description 15:0 vendor identification number . this is a 16-bit value assigned to intel. intel vid = 8086h. 3.4.2. did?device identification register (device 0) address offset: 02?03h default value: 1a21h attribute: read only size: 16 bits this 16-bit register combined with the vendor identification register uniquely identifies any pci device. writes to this register have no effect. bit description 15:0 device identification number . this is a 16 bit value assigned to the mch host-hub interface a bridge/dram controller function #0. did = 1a21h for the mch device 0.
82840 mch r datasheet 45 3.4.3. pcicmd?pci command register (device 0) address offset: 04?05h default: 0006h access: read/write, read only size 16 bits since mch device 0 does not physically reside on pci0 many of the bits are not implemented. writes to not implemented bits have no affect. bit descriptions 15:10 reserved. 9 fast back-to-back?ro: (not implemented). hardwired to 0. this bit controls whether or not the master can do fast back-to-back writes. since device 0 is strictly a target, this bit is not implemented. 8 serr enable (serre)?r/w: this bit is a global enable bit for device 0 serr messaging. the mch does not have an serr# signal. the mch communicates the serr# condition by sending a serr message to the ich. 1 = enable. the mch is enabled to generate serr messages over the hub interface for specific device 0 error conditions that are individually enabled in the errcmd register. the error status is reported in the errsts and pcists registers. 0 = the serr message is not generated by the mch for device 0. note: this bit only controls serr message for the device 0. devices 1 and 2 have their own serre bits to control error reporting for error conditions occurring on their respective devices. 7 address/data stepping?ro: (not implemented). hardwired to 0. address/data stepping is not implemented in the mch. 6 parity error enable (perre)?r/w: 1 = detection of a parity error by the mch on the hub interface a results in an serr message being sent to the ich, if the serre bit (bit 9 of this register) is also set. 0 = parity errors detected on hub interface a by the mch do not result in an serr message. 5 vga palette snoop?ro: (not implemented). hardwired to 0. 4 memory write and invalidate enable(mwie)?ro: (not implemented). hardwired to 0. 3 special cycle enable(sce)?ro: (not implemented). hardwired to 0. 2 bus master enable (bme) ?ro: (not implemented). hardwired to 1. the mch is always enabled as a master on hub interface a. 1 memory access enable (mae) ?ro: (not implemented). hardwired to 1. the mch always allows access to main memory. 0 i/o access enable (ioae)?ro: (not implemented). hardwired to a 0.
46 datasheet 3.4.4. pcists?pci status register (device 0) address offset: 06?07h default value: 0090h access: read only, read/write clear size: 16 bits pcists is a 16-bit status register that reports the occurrence of error events on device 0s on the hub interface. bits 15:12 are read/write clear. all other bits are read only. since the mch device 0 is the host-to-hub interface a bridge, many of the bits are not implemented. bit descriptions 15 detected parity error (dpe)?r/wc: 1 = the mch detects a parity error on the hub interface a. 0 = software clear this bit by writing a 1 to it. 14 signaled system error (sse)?r/wc: 1 = the mch device 0 generates a serr message over the hub interface a for any enabled device 0 error condition. device 0 error conditions are enabled in the pcicmd and errcmd registers. device 0 error flags are read/reset from the pcists or errsts registers. 0 = software clears this bit by writing a 1 to it. 13 received master abort status (rmas)?r/wc: 1 = this bit is set when the mch generates a request over the hub interface a and receives a master abort completion packet. 0 = software clears this bit by writing a 1 to it. 12 received target abort status (rtas)?r/wc: 1 = the mch generates a request over the hub interface a and receives a target abort completion packet. 0 = software clears this bit by writing a 1 to it. 11 signaled target abort status (stas)?ro: (not implemented). hardwired to a 0. the mch does not generate a target abort completion packet over the hub interface a. 10:9 devsel# timing (devt)?ro: (not implemented). hardwired to a 00. the hub interface does not use devsel# protocol. 8 data parity detected (dpd)?ro: (not implemented). hardwired to 0. 7 fast back-to-back (fb2b)?ro: (not implemented). hardwired to 1. 6:5 reserved. 4 capability list (clist)?ro: 1 = indicates to the configuration software that this device/function implements a list of new capabilities. a list of new capabilities is accessed via register capptr at configuration address offset 34h. register capptr contains an offset pointing to the start address within configuration space of this device where the agp capability standard register resides. 3:0 reserved.
82840 mch r datasheet 47 3.4.5. rid?revision identification register (device 0) address offset: 08h default value: 00h access: read only size: 8 bits this register contains the revision number of the mch device 0. these bits are read only and writes to this register have no effect. bit description 7:0 revision identification number . this is an 8-bit value that indicates the revision identification number for the mch device 0. for the a-0 stepping, this value is 00h. 3.4.6. subc?sub-class code register (device 0) address offset: 0ah default value: 00h access: read only size: 8 bits this register contains the sub-class code for the mch device 0. this code is 00h indicating a host bridge device. the register is read only. bit description 7:0 sub-class code (subc) . this is an 8-bit value that indicates the category of bridge for the mch. 00h = host bridge. 3.4.7. bcc?base class code register (device 0) address offset: 0bh default value: 06h access: read only size: 8 bits this register contains the base class code of the mch device 0. bit description 7:0 base class code (basec): this is an 8-bit value that indicates the base class code for the mch. 06h = bridge device.
48 datasheet 3.4.8. mlt?master latency timer register (device 0) address offset: 0dh default value: 00h access: read only size: 8 bits the hub interface does not use a master latency timer. therefore, this register is not implemented. bit description 7:0 these bits are hardwired to 0. writes have no effect. 3.4.9. hdr?header type register (device 0) offset: 0eh default: 00h access: read only size: 8 bits this register identifies the header layout of the configuration space. no physical register exists at this location. bit descriptions 7:0 this read only field always returns 0 when read and writes have no affect. 3.4.10. apbase?aperture base configuration register (device 0) offset: 10 ? 13h default: 00000008h access: read/write, read only size: 32 bits the apbase is a standard pci base address register that is used to set the base of the graphics aperture. the standard pci configuration mechanism defines the base address configuration register such that only a fixed amount of space can be requested (dependent on which bits are hardwired to 0 or behave as hardwired to 0). to allow for flexibility (of the aperture), an additional register called apsize is used as a ?back-end? register to control which bits of the apbase will behave as hardwired to 0. this register is programmed by the mch specific bios code that runs before any of the generic configuration software is run. note: bit 9 of the mchcfg register is used to prevent accesses to the aperture range before this register is initialized by the configuration software and the appropriate translation table structure has been established in the main memory.
82840 mch r datasheet 49 bit description 31:28 upper programmable base address bits?r/w: these bits are used to locate the range size selected via bits 27:4 of this register. default = 0000 27:22 lower ?hardwired?/programmable base address bits: these bits behave as a ?hardwired? or as a programmable depending on the contents of the apsize register as defined below: 27 26 25 24 23 22 aperture size r/w r/w r/w r/w r/w r/w 4 mb r/w r/w r/w r/w r/w 0 8 mb r/w r/w r/w r/w 0 0 16 mb r/w r/w r/w 0 0 0 32 mb r/w r/w 0 0 0 0 64 mb r/w 0 0 0 0 0 128 mb 0 0 0 0 0 0 256 mb bits 27:22 are controlled by bits 5:0 of the apsize register in the following manner: if bit apsize[5]=0, apbase[27]=0; if apsize[5]=1, apbase[27]=r/w (read/write). the same applies correspondingly to other bits. default for apsize[5:0]=000000b forcing default apbase[27:22] =000000b (i.e., all bits respond as ?hardwired? to 0). this provides a default to the maximum aperture size of 256 mb. the mch specific bios is responsible for a selecting smaller size (if required) before pci configuration software runs and establishes the system address map. 21:4 hardwired to 0s. this forces minimum aperture size selected by this register to be 4 mb. 3 prefetchable?ro: hardwired to 1. 1 = prefetchable (i.e., there are no side effects on reads, the device returns all bytes on reads regardless of the byte enables, and the mch may merge processor writes into this range without causing errors). 2:1 type?ro: hardwired to 00. these bits determine addressing type. 00 = address range defined by the upper bits of this register can be located anywhere in the 32-bit address space. 0 memory space indicator?ro: hardwired to 0. 0 = memory range (aperture range is a memory range).
50 datasheet 3.4.11. svid?subsystem vendor id (device 0) offset: 2c?2dh default: 0000h access: read/write once size: 16 bits this value is used to identify the vendor of the subsystem. bit description 15:0 subsystem vendor id?r/wo: the default value is 00h. this field should be programmed during boot- up. after this field is written once, it becomes read only. 3.4.12. sid?subsystem id (device 0) offset: 2e?2fh default: 0000h access: read/write once size: 16 bits this value is used to identify a particular subsystem. bit description 15:0 subsystem id?r/wo: the default value is 00h. this field should be programmed during boot-up. after this field is written once, it becomes read only. 3.4.13. capptr?capabilities pointer (device 0) offset: 34h default: a0h access: read only size: 8 bits the capptr provides the offset that is the pointer to the location where the agp standard registers are located. bit description 7:0 start of agp standard register block: this field is a pointer to the start of agp standard register block. a0h = start of agp standard register block.
82840 mch r datasheet 51 3.4.14. gar[15:0]?rdram group architecture register (device 0) address offset: 40?4fh default value: 80h access: read/write size: 8 bits/register this 8-bit register defines the page size, the #of banks, and dram technology of each device group in the rdram channel. there are 16 gar registers (gar0 ? gar15). in single channel-pair operation, only the first eight are used to describe the 32 device-pairs, where each register describes a group of 4 rdram device pairs. in multiple channel-pair mode, all 16 registers are used to describe memory device-pair groups. since there can be four times as many devices in this mode and the number of descriptive registers is only doubled, each register describes twice as many register-pairs (8 device- pairs/group). note: this register is locked and becomes read only when the d_lck bit in the smram register is set. this is done for improve smm security. bit description 7:6 device page size (dps) . this field defines the page size of the each device in the corresponding group. 00 = reserved 01 = reserved 10 = 1 kb 11 = 2 kbs 5 reserved 4 device banks (db): this field defines # of bank architecture in each device in the group. 0 = 16 dependent banks 1 = 32 dependent banks arranged in two groups of 16 dependent banks (i.e., 2x16) 3 reserved 2:1 device dram technology (ddt): this field defines the dram technology of eachdevice in the group. 00 = 64/72mbit 01 = 128/144mbit 10 = 256/288mbit 11 = reserved 0 reserved.
52 datasheet 3.4.15. mchcfg?mch configuration register (device 0) offset: 50?51h default: 00s0_0000_ 0000-_0s00b access: read/write once, read/write, read only size: 16 bits bit description 15:14 reserved 13: host frequency?ro: these bits are used to determine the host frequency. these bits are set by an external strapping option at reset and are read only. 0 = 100 mhz 1 = 133 mhz 12 reserved 11 direct rambus frequency?r/w: these bits are written by the bios after polling the rambus* direct rdrams and finding the least common denominator speed. 0 = 300 mhz 1 = 400 mhz 10 reserved 9 aperture access global enable?r/w: this bit is used to prevent access to the aperture from any port (host, pci0 or agp) before the aperture range is established by the configuration software and appropriate translation table in the main dram has been initialized. default is 0. this bit must be set after system is fully configured for aperture accesses. 1 = enable 0 = disable 8:7 dram data integrity mode (ddim)?r/w: these bits select one of 3 dram data integrity modes. 00 = non-ecc (byte-wise writes supported, rdram device only) (default) 01 = reserved 10 = ecc mode (generation and error checking/correction) 11 = ecc mode with hardware scrubbing enabled. same as ddim=10, plus corrected data written to dram. 6 ecc diagnostic mode enable (edme)?r/w: 1 = enable. mch enters ecc diagnostic test mode. on all subsequent write cycles to main memory, the mch will write all zeroes to the ecc field. this allows straightforward creation of both single bit and multiple bit errors. 0 = disable. normal operating mode (default).
82840 mch r datasheet 53 bit description 5 mda present (mdap)?r/w: this bit works with the vga enable bit in the bctrl register of device 1and 2 to control the routing of host initiated transactions targeting mda compatible i/o and memory address ranges. this bit should not be set when the vga enable bit is not set in either device 1 or 2. if the vga enable bit is set, then accesses to io address range x3bch?x3bfh are forwarded to the hub interface a. mda resources are defined as the following: memory: 0b0000h ? 0b7fffh i/o: 3b4h, 3b5h, 3b8h, 3b9h, 3bah, 3bfh, (including isa address aliases, a[15:10] are not used in decode) any i/o reference that includes the i/o locations listed above, or their aliases, are forwarded to the hub interface a, even if the reference includes i/o locations not listed above. refer to the system address map chapter for further information. 4 reserved. 3 agp i/o buffer mode?ro: the mch has an internal circuit that detects the voltage level on the agpi/o buffer vddq rail. 0 = agp vddq is 1.5v. 1 = agp vddq is 3.3v. 2 in-order queue depth (ioqd)?ro: this bit reflects the value sampled on ha7# on the deassertion of the cpurst#. it indicates the depth of the host bus in-order queue (i.e., level of host bus pipelining). if ioqd is set to 1 (ha7# sampled 1; i.e., undriven on the host bus), the depth of the host bus in-order queue is configured to the maximum allowed by the host bus protocol (i.e., 8). if the ioqd bit is set to 0 (ha7# is sampled asserted; i.e., 0), the depth of the host bus in-order queue is set to 1 (i.e., no pipelining support on the host bus). note that ha7# is not driven by the mch during cpurst#. if an ioq size of 1 is desired, ha7# must be driven low during cpurst# by an external source. 1:0 reserved. 3.4.16. fdhc?fixed dram hole control register (device 0) address offset: 58h default value: 00h access: read/write size: 8 bits this 8-bit register controls a fixed dram hole: 15?16 mb. bit description 7 hole enable (hen): this field enables a memory hole in dram space. host cycles matching an enabled hole are passed on to ich through the hub interface. the hub interface cycles matching an enabled hole will be ignored by the mch. note that a selected hole is not re-mapped. 1 = enable. 15 mb ? 16 mb (1mb) 0 = disable 6:0 reserved.
54 datasheet 3.4.17. pam0?pam6?programmable attribute map registers (device 0) address offset: 59?5fh (pam0?pam6) default value: 00h attribute: read/write size: 8 bits the mch allows programmable memory attributes on 13 legacy memory segments of various sizes in the 640 kb to 1 mb address range. seven programmable attribute map (pam) registers are used to support these features. cacheability of these areas is controlled via the mtrr registers in the processor. two bits are used to specify memory attributes for each memory segment. these bits apply to host initiator only access to the pam areas. the 82840 mch will respond to a ?master abort? for any agp, pci, or hub interface a/b initiated accesses to the pam areas. these attributes are: re read enable. when re = 1, the host read accesses to the corresponding memory segment are claimed by the mch and directed to main memory. conversely, when re = 0, the host read accesses are directed to pci0. we write enable. when we = 1, the host write accesses to the corresponding memory segment are claimed by the mch and directed to main memory. conversely, when we = 0, the host write accesses are directed to pci0. the re and we attributes permit a memory segment to be read only, write only, read/write, or disabled. for example, if a memory segment has re = 1 and we = 0, the segment is read only. each pam register controls two regions; typically, 16 kbs in size. each of these regions has a 4-bit field. the four bits that control each region have the same encoding and are defined in table 3. table 3. attribute bit assignment bits [7, 3] reserved bits [6, 2] reserved bits [5, 1] we bits [4, 0] re description x x 0 0 disabled. dram is disabled and all accesses are directed to the hub interface a. the mch does not respond as a pci target for any read or write access to this area. x x 0 1 read only. reads are forwarded to dram and writes are forwarded to the hub interface a for termination. this write protects the corresponding memory segment. the mch will respond as an agp or the hub interface a target for read accesses but not for any write accesses. x x 1 0 write only. writes are forwarded to dram and reads are forwarded to the hub interface for termination. the mch will respond as an agp or hub interface a target for write accesses but not for any read accesses. x x 1 1 read/write. this is the normal operating mode of main memory. both read and write cycles from the host are claimed by the mch and forwarded to dram. the mch will respond as an agp or the hub interface a target for both read and write accesses.
82840 mch r datasheet 55 as an example, consider a bios that is implemented on the expansion bus. during the initialization process, the bios can be shadowed in main memory to increase the system performance. when bios is shadowed in main memory, it should be copied to the same address location. to shadow the bios, the attributes for that address range should be set to write only. the bios is shadowed by first doing a read of that address. this read is forwarded to the expansion bus. the host then does a write of the same address, which is directed to main memory. after the bios is shadowed, the attributes for that memory area are set to read only so that all writes are forwarded to the expansion bus. table 4 and figure 4 shows the pam registers and the associated attribute bits. figure 2. pam registers pam re we re r r we r r 76543210 pam 6 pam5 pam4 pam3 pam2 pam1 pam0 read enable ( r/ 1=enable 0=disable write enable (r/w) 1=enable 0=disable reserved reserved read enable (r/w) 1=enable 0=disable write enable (r/w) 1=enable 0=disable reserved reserved 5fh 5eh 5dh 5ch 5bh 5ah 59h offset table 4. pam registers and associated memory segments pam reg attribute bits memory segment comments offset pam0[3:0] reserved 59h pam0[7:4] r r we re 0f0000h?0fffffh bios area 59h pam1[3:0] r r we re 0c0000h?0c3fffh isa add-on bios 5ah pam1[7:4] r r we re 0c4000h?0c7fffh isa add-on bios 5ah pam2[3:0] r r we re 0c8000h?0cbfffh isa add-on bios 5bh pam2[7:4] r r we re 0cc000h?0cffffh isa add-on bios 5bh pam3[3:0] r r we re 0d0000h?0d3fffh isa add-on bios 5ch pam3[7:4] r r we re 0d4000h?0d7fffh isa add-on bios 5ch pam4[3:0] r r we re 0d8000h?0dbfffh isa add-on bios 5dh pam4[7:4] r r we re 0dc000h?0dffffh isa add-on bios 5dh pam5[3:0] r r we re 0e0000h?0e3fffh bios extension 5eh pam5[7:4] r r we re 0e4000h?0e7fffh bios extension 5eh pam6[3:0] r r we re 0e8000h?0ebfffh bios extension 5fh pam6[7:4] r r we re 0ec000h?0effffh bios extension 5fh for details on overall system address mapping scheme, see the system address map chapter.
56 datasheet dos application area (00000h?9fffh) the dos area is 640 kb and it is divided into two parts. the 512 kb area at 0 to 7ffffh is always mapped to the main memory controlled by the mch, while the 128 kb address range from 080000 to 09ffffh can be mapped to pci0 or to main dram. by default this range is mapped to main memory and can be declared as a main memory hole (accesses forwarded to pci0) via mch fdhc configuration register. video buffer area (a0000h?bffffh) this 128 kb area is not controlled by attribute bits. the host -initiated cycles in this region are always forwarded to either pci0 or agp unless this range is accessed in smm mode. routing of accesses is controlled by the legacy vga control mechanism of the ?virtual? pci-pci bridge device in the mch. this area can be programmed as smm area via the smram register. when used as a smm space, this range can not be accessed from the hub interface nor agp. expansion area (c0000h?dffffh) this 128 kb area is divided into eight 16 kb segments that can be assigned with different attributes via pam control register. extended system bios area (e0000h?effffh) this 64 kb area is divided into four 16 kb segments which can be assigned with different attributes via pam control register. system bios area (f0000h?fffffh) this area is a single 64 kb segment which can be assigned with different attributes via pam control register.
82840 mch r datasheet 57 3.4.18. gba0?gba15?rdram group boundary address register (device 0) address offset: 60?7fh (gba0?gba15) default: 01h access: read/write size 16 bits/register note: this register is locked and becomes read only when the d_clk bit in the smram register is set. this is done to improve smm security. the rdram device-pairs are logically arranged into groups. there are eight groups when the mch is configured for single channel-pair mode operation; there are four groups for multiple channel-pair mode operation. each group requires a separate gba register. the gba registers define group id and the upper and lower addresses for each group in a channel-pair. contents of bits 0:9 of this register represent the boundary addresses in 16 mb granularity. for example, a value of 01h indicates that the programmed group applies to memory below 16 mb. only the first eight gba registers are used in single channel-pair mode. all 16 gba registers are used in multiple channel-pair mode. note that gba15 must always contain the group boundary address that points to the top of memory, whether the mch is being used in single channel-pair mode or multiple channel-pair mode. 60?61h gba0 = total memory in group0 (in 16 mbs) 62?63h gba1 = total memory in group0 + group1 (in 16 mbs) 64?65h gba2 = total memory in group0 + group1 + group2 (in 16 mbs) 66?67h gba3 = total memory in group0 + group1 + group2 + group3 (in 16 mbs) .... 7e ? 7fh gba15 = total memory in group0 + group1 + group2 + ? + group15 (in 16 mbs) bit description 15 reserved. 14:13 channel id (chid): reflects the id of the rambus* channel described by this gba entry. this field is only used when mrh-r is present. 12:10 group id (gid): this 3-bit value is used to identify a logical group of direct rdram devices. this value and appropriate address bits are used to generate the device rdram_d device id. note that all device-pairs populated in a group must be of the same memory technology. 9:0 group boundary address (gba): this 10-bit value is compared against address lines a[33:24] to determine the upper address limit of a particular group of devices (i.e., gba minus previous gba = group size).
58 datasheet 3.4.19. rdps?rdram pool sizing register (device 0) address offset: 88h default value: 10h access: read/write size: 8 bits bit description 7 pool lock (lock): 1 = contents of the rdps register becomes read only. 0 = contents of the rdps register becomes read/write. 6 reserved 5 reinitialize rdram pools (poolinit): 1 = rdram pools are reinitialized to the default value contained in this register. 0 = as long as this bit is 0, the other fields in this register may be modified without changing the behavior of the pools. this bit is set to 0 after the rdram devices are initialized with the new pool settings and the mch is operated in the new pool settings. note that the external thermal sensor trip conditions (i.e., a rising edge on overt# or rdram devices report an overtemperature condition) do not have any effect on this bit, even though they do cause new pool values to be loaded. 4 pool c operating mode (pcs) : 1 = all devices found neither in pool a nor in pool b are assumed to be in nap mode. 0 = all devices in pool c are assumed to be in standby mode. 3:2 pool a capacity (pac): this field defines the maximum number of rdram devices that can reside in pool a at a time. 00 = 1 01 = 2 10 = 4 11 = 8 1:0 pool b capacity (pbc): this field defines the maximum number of rdram devices that can reside in pool b at a time. 00 = 1 01 = 4 10 = 8 11 = 16
82840 mch r datasheet 59 3.4.20. drd?rdram device register data register (device 0) address offset: 90?93h default value: 0000h access: read/write size: 32 bits bit description 31:0 register data (rd): bits 31:0 contain the 32 bits of data to be written to a rdram register or the data read from a rdram register as a result of iop execution. data is valid when the iio bit of the ricm register has transitioned from 1 to 0. bits 31:16 apply to direct rambus* interface a and bits 15:0 apply to direct rambus* interface b. 3.4.21. ricm?rdram initialization control management register (device 0) address offset: 94?97h default value: 00000000h access: read/write size: 32 bits bit description 31 reserved 30 rambus* interface b stick channesl swap: 1 = swap. the two stick channels of each mrh-r are swapped on the rambus* interface b. 0 = not swapped. 29:28 time to powerup(tpu): this field defines the total powerdown exit time for rdram devices and corresponds to the rdram device (pdna+tpdnb) timing. 00 = 42.0 us 01 = 34.5 us 10 = 27.0 us 11 = 19.5 us 27 initialization complete (ic): 1 = bios sets this bit to 1 after the initialization of the rdram memory array is complete. 26:25 reserved 24 mrh-r present (mrhrp): 1 = set by software when it detects the presence of memory repeater hub for rambus* component in the system. 23 initiate initialization operation (iio): the software must check to see if this bit is 0 before writing to this bit. the operations which specify register data read from the direct rdram will have the data valid in drd register when this bit is cleared to 0. 1 = execution of the intialization operation specified by iop starts. 0 = after the execution is completed, the mch clears this bit to 0. 22 reserved
60 datasheet bit description 21:20 channel id (cid): this field specifies the channel address for which the initialization or the channel reset operation is initialed. 19 broadcast address (ba): 1 = initialization operation (iop) is broadcast to all devices. when this bit is set to 1, the dsa field is don?t care. 18:10 device register address (dra): this field specifies the register address for the register read and write operations. 9:5 serial device/channel address (sdca): this 5 bits field specifies the serial device id of the direct rdram to which the intialization operation is targeted for the next sio command to be sent by mch. 4:0 initialization opcode (iop): this field specifies the initialization operartion to be done on direct rdram device. 00000 = rdram register read 00001 = rdram register write 00010 = rdram set reset 00011 = reserved 00100 = rdram set fast clock mode 00101 = rdram temperature calibrate enable 00110 = rdram temperature calibrate 00111 = reserved 01000 = redirect next sio 01001 = mrh-r ?stick channel? sio reset 01010 = reserved 01011 = rdram clear reset 01100 = reserved 01101 = write spd register 01110 = read spd register 01111 = reserved 10000 = rdram current calibration 10001 = rdram sio reset 10010 = rdram powerdown exit 10011 = rdram powerdown entry 10100 = rdram nap entry 10101 = rdram nap exit 10110 = rdram refresh 10111 = rdram precharge 11000 = manual current calibration of mch rac 11001 = mch rac load rac a configuration register 11010 = mch rac load rac b configuration register 11011 = initialize mch rac 11100 = mch rac current calibration 11101 = mch rac thermal calibration 11110 = reserved 11111 = powerup all sequence
82840 mch r datasheet 61 3.4.22. mch expansion rac a/b configuration registers address offset not applicable (see description below) default: 0000_0000h access: not applicable (see description below) size: 32 bits to enable the e-clamp of mch rac a, first write a 32-bit value into the drd register (offset 90?93h). then, issue an initialization opcode (iop=11001b) thro ugh the ricm/sicm register (offset 94?97h). repeat the same procedure above for enabling the e-clamp on mch rac b (iop=11010b). the default state of the e-clamps are disabled after power on. bit description 31:26 reserved 25:24 early clamp enable: 00 = disabled 11 = enabled 01 or 10 = reserved 23:0 reserved 3.4.23. smram?system management ram control register (device 0) address offset: 9dh default value: 02h access: read/write, read only size: 8 bits the smramc register controls how accesses to compatible and extended smram spaces are treated. the open, close, and lock bits function only when g_smrame bit is set to a 1. also, the open bit must be reset before the lock bit is set. bit description 7 reserved 6 smm space open (d_open): when d_open=1 and d_lck=0, the smm space dram is made visible even when smm decode is not active. this is intended to help bios initialize smm space. software should ensure that d_open=1 and d_cls=1 are not set at the same time. when d_lck is set to a 1, d_open is reset to 0 and becomes read only. 5 smm space closed (d_cls): when d_cls = 1 smm space dram is not accessible to data references, even if smm decode is active. code references may still access smm space dram. this will allow smm software to reference "through" smm space to update the display even when smm is mapped over the vga range. software should ensure that d_open=1 and d_cls=1 are not set at the same time. 4 smm space locked (d_lck): when d_lck is set to 1, then d_open is reset to 0 and d_lck, d_open, c_base_seg, h_smram_en, tseg_sz and tseg_en become ?read only?. d_lck can be set to 1 via a normal configuration space write but can only be cleared by a full reset. the combination of d_lck and d_open provide convenience with security. bios can use the d_open function to initialize smm space and then use d_lck to "lock down" smm space in the future so that no application software (or bios itself) can violate the integrity of smm space, even if the program has knowledge of the d_open function.
62 datasheet bit description 3 global smram enable (g_smrame): if set to a 1, then compatible smram functions is enabled, providing 128 kb of dram accessible at the a0000h address while in smm (ads# with smm decode). to enable extended smram function this bit has be set to 1. refer to the system address map chapter for more details. once d_lck is set, this bit becomes read only. 1 = enable 0 = disable 2:0 compatible smm space base segment (c_base_seg)?ro: this field indicates the location of smm space. "smm dram" is not remapped. it is simply "made visible" if the conditions are right to access smm space, otherwise the access is forwarded to the hub interface. c_base_seg is hardwired to 010 to indicate that the mch supports the smm space at a0000h-bffffh. 3.4.24. esmramc?extended system management ram control register (device 0) address offset: 9eh default value: 38h access: read/write/lock size: 8 bits the extended smram register controls the configuration of extended smram space. the extended smram (e_smram) memory provides a write-back cacheable smram memory space that is above 1 mb. bit description 7 h_smram_en (h_smrame): controls the smm memory space location (i.e., above 1 mb or below 1 mb). when g_smrame is 1 and h_smrame is set to 1, the high smram memory space is enabled. smram accesses from 0ffea0000h to 0ffebffffh are remapped to dram address 000a0000h to 000bffffh. once d_lck is set, this bit becomes read only. 6 e_smram_err (e_smerr): this bit is set when the host accesses the defined memory ranges in extended smram (high memory and t-segment) while not in smm space and with the d-open bit = 0. it is software?s responsibility to clear this bit. software must write a 1 to this bit to clear it 5 smram_cache (sm_cache): hardwired to 1. 4 smram_l1_en (sm_l1): hardwired to 1. 3 smram_l2_en (sm_l2): hardwired to 1. 2:1 tseg_sz[1-0] (t_sz): selects the size of the tseg memory block, if enabled. this memory is taken from the top of dram space (i.e., tom - tseg_sz), which is no longer claimed by the memory controller (if tseg_en is set, all accesses to this space are sent to the hub interface). this field decodes as follows: 00 = (tom-128k) to tom 01 = (tom-256k) to tom 10 = (tom-512k) to tom 11 = (tom-1m) to tom once d_lck is set, this bit becomes read only. 0 tseg enable (tseg_en): enabling of smram memory (tseg, 128 kb, 256 kb, 512 kb or 1 mb of additional smram memory) for extended smram space only. when g_smrame =1 and tseg_en = 1, the tseg is enabled to appear in the appropriate physical address space. once d_lck is set, this bit becomes read only. tseg_en can only be 1 when g_smrame is 1.
82840 mch r datasheet 63 3.4.25. acapid?agp capability identifier register (device 0) address offset: a0?a3h default value: 00200002h / 00000000h access: read only size: 32 bits this register provides standard identifier for agp capability. bit description 31:24 reserved 23:20 major agp revision number: these bits provide a major revision number of agp specification to which this version of mch conforms. 0010 = rev 2.x. 19:16 minor agp revision number: these bits provide a minor revision number of agp specification that this version of the mch conforms. this number is hardwired to value of ?0000? (i.e., implying rev x.0). together with major revision number this field identifies mch as an agp rev 2.0 compliant device. 0000 = rev x.0 15:8 next capability pointer: agp capability is the first and the last capability described via the capability pointer mechanism. hardwired to 0s. 0000_0000 = end of the capability linked list 7:0 agp capability id: this field identifies the linked list item as containing agp registers. 0000_0010 = assigned by the pci sig.
64 datasheet 3.4.26. agpstat?agp status register (device 0) address offset: a4?a7h default value: 1f000217h access: read only size: 32 bits this register reports agp device capability/status. bit description 31:24 maximum requests (rq): hardwired to 1fh. this field contains the maximum number of agp command requests the mch is configured to manage. the lower 6 bits of this field reflect the value programmed in agpctrl[12:10]. only discrete values of 32, 16, 8, 4 , 2 and 1 can be selected via agpctrl. upper bits are hardwired to 0s. 1fh = a maximum of 32 outstanding agp command requests can be handled by the mch 23:10 reserved 9 sideband addressing (sba): hardwired to 1. 1 = mch supports side band addressing. 8:6 reserved 5 4 gb maximum address space (4gb): hardwired to 0. 0 = mch does not support addresses greater than 4 gigabytes. 4 fast writes (fw): hardwired to 1. 1 = mch supports fast writes from the host to the agp master. 3 reserved 2:0 rate: after reset, the mch reports its data transfer rate capability. bit 0 identifies if agp device supports 1x data transfer mode, bit 1 identifies if agp device supports 2x data transfer mode, bit 2 identifies if agp device supports 4x data transfer mode. note that the selected data transfer mode apply to both ad bus and sba bus. it also applies to fast writes, if they are enabled. 111 = 1x, 2x, and 4x data transfer modes supported
82840 mch r datasheet 65 3.4.27. agpcmd?agp command register (device 0) address offset: a8?abh default value: 00000000h access: read/write size: 32 bits this register provides control of the agp operational parameters. bit description 31:10 reserved. 9 side band addressing enable (sba_en): 1 = enable. side band addressing mechanism is enabled. 0 = disable 8 agp enable: when this bit is set to 0, the mch ignores all agp operations, including the sync cycle. any agp operations received while this bit is set to 1 will be serviced, even if this bit is reset to 0. if this bit transitions from a 1 to a 0 on a clock edge in the middle of an sba command being delivered in 1x mode, the command will be issued. when this bit is set to 1, the mch responds to agp operations delivered via pipe# or to operations delivered via sba, if the agp side band addressing enable bit is also set to 1. 1 = enable 0 = disable 7:6 reserved. 5 4 gb maximum address space (4gb): hardwired to 0. 0 = the mch, as an agp target, does not support addressing greater than 4 gbs. 4 fast writes enable (fw_en): 1 = the mch uses the fast write protocol for memory write transactions from the mch to the agp master. fast writes occur at the data transfer rate selected by the data rate bits (2:0) in this register. 0 = when this bit is 0 (or when the data rate bits are set to 1x mode), the memory write transactions from the mch to the agp master use standard pci protocol. 3 reserved. 2:0 data rate: the settings of these bits determines the agp data transfer rate. one (and only one) bit in this field must be set to indicate the desired data transfer rate. bit 0: 1x, bit 1: 2x, bit 2: 4x. the same bit must be set on both master and target. configuration software will update this field by setting only one bit that corresponds to the capability of the agp master (after that capability has been verified by accessing the same functional register within the agp masters configuration space.) note that this field applies to ad and sba buses. it also applies to fast writes, if they are enabled. 001 = 1x 010 = 2x 100 = 4x all other combinations are illegal.
66 datasheet 3.4.28. agpctrl?agp control register (device 0) address offset: b0?b3h default value: 00000000h access: read/write size: 32 bits this register provides for additional control of the agp interface. bit description 15:8 reserved 7 gtlb enable (and gtlb flush control)?r/w: 1 = enable. normal operations of the graphics translation lookaside buffer. 0 = disable (default). gtlb is flushed by clearing the valid bits associated with each entry. 6:0 reserved. 3.4.29. apsize?aperture size (device 0) address offset: b4h default value: 00h access: read/write size: 8 bits apsize determines the effective size of the graphics aperture used for a particular mch configuration. this register can be updated by the mch specific bios configuration sequence before the pci standard bus enumeration sequence takes place. if the register is not updated, the default value selects an aperture of maximum size (i.e., 256 mb). the size of the table that corresponds to a 256 mb aperture is not practical for most applications; therefore, these bits must be programmed to a smaller practical value that forces adequate address range to be requested via the apbase register from the pci configuration software. bit description 7:6 reserved 5:0 graphics aperture size (apsize)?r/w: each bit in apsize[5:0] operates on similarly ordered bits in apbase[27:22] of the aperture base configuration register. when a particular bit of this field is 0, it forces the similarly ordered bit in apbase[27:22] to behave as ?hardwired? to 0. when a particular bit of this field is set to 1, it allows the corresponding bit of the apbase[27:22] to be read/write accessible. only the following combinations are allowed: 5 4 3 2 1 0 aperture size 1 1 1 1 1 1 4 mb 1 1 1 1 1 0 8 mb 1 1 1 1 0 0 16 mb 1 1 1 0 0 0 32 mb 1 1 0 0 0 0 64 mb 1 0 0 0 0 0 128 mb 0 0 0 0 0 0 256 mb default for apsize[5:0]=000000b forces default apbase[27:22] =000000b (i.e., all bits respond as ?hardwired? to 0). this provides maximum aperture size of 256 mb. as another example, programming apsize[5:0]=111000b hardwires apbase[24:22]=000b while enabling apbase[27:25] as read/write programmable.
82840 mch r datasheet 67 3.4.30. attbase ? ? ? ? aperture translation table base register (device 0) address offset: b8?bbh default value: 00000000h access: read/write size: 32 bits this register provides the starting address of the graphics aperture translation table base located in the main dram. this value is used by the mch graphics aperture address translation logic (including the gtlb logic) to obtain the appropriate address translation entry required during the translation of the aperture address into a corresponding physical dram address. the attbase register may be dynamically changed. note: the address provided via attbase is 4 kb aligned. bit description 31:12 address translation table base pointer: this field contains a pointer to the base of the translation table used to map memory space addresses in the aperture range to addresses in main memory. 11:0 reserved 3.4.31. amtt?agp interface multi-transaction timer register (device 0) address offset: bch default value: 00h access: read/write size: 8 bits amtt is an 8-bit register that controls the amount of time that the mch arbiter allows an agp master to perform multiple back-to-back transactions. the mch amtt mechanism is used to optimize the performance of the agp master (using pci protocol) that performs multiple back-to-back transactions to fragmented memory ranges (and as a consequence it can not use long burst transfers). the amtt mechanism applies to the host-agp transactions as well and it guarantees to the processor a fair share of the agp interface bandwidth. the number of clocks programmed in the amtt represents the guaranteed time slice (measured in 66 mhz clocks) allotted to the current agent (either agp master or host bridge) after which the agp arbiter will grant the bus to another agent. the default value of 00h disables this function. the amtt value can be programmed with 8 clock granularity. for example, if the amtt is programmed to 18h, the selected value corresponds to the time period of 24 agp (66 mhz) clocks. bit description 7:3 multi-transaction timer count value: the value programmed in this field represents the guaranteed time slice (measured in eight 66 mhz clock granularity) allotted to the current agent (either agp master or mch) after which the agp arbiter will grant the bus to another agent. 2:0 reserved.
68 datasheet 3.4.32. lptt?low priority transaction timer register (device 0) address offset: bdh default value: 00h access: read/write size: 8 bits lptt is an 8-bit register similar in a function to amtt. this register is used to control the minimum tenure on the agp for low priority data transaction (both reads and writes) issued using pipe# or sb mechanisms. the number of clocks programmed in the lptt represents the guaranteed time slice (measured in 66 mhz clocks) allotted to the current low priority agp transaction data transfer state. this does not necessarily apply to a single transaction but it can span over multiple low-priority transactions of the same type. after this time expires, the agp arbiter may grant the bus to another agent, if there is a pending request. the lptt does not apply in the case of high-priority request where ownership is transferred directly to high-priority requesting queue. the default value of 00h disables this function. the lptt value can be programmed with 8 clock granularity. for example, if the lptt is programmed to 10h, the selected value corresponds to the time period of 16 agp (66 mhz) clocks. bit description 7:3 low priority transaction timer count value: the number of clocks programmed in these bits represents the guaranteed time slice (measured in eight 66 mhz clock granularity) allotted to the current low priority agp transaction data transfer state. 2:0 reserved.
82840 mch r datasheet 69 3.4.33. rdtr?rdram timing register (device 0) address offset: beh default value: 00h access: read/write size: 8 bits rdtr defines the timing parameters for all devices in the direct rdram channel. bios programs this register with the ?least common denominator? values after reading configuration registers of each device in the direct rdram channel. this register applies to the entire dram array. bit description 7:6 row to column delay (trcd): this field defines the minimum interval between opening a row and column operation on that row in units of direct rambus* clo cks (rclks). 00 = reserved 01 = 7 10 = 9 11 = reserved 5:0 rdram total cas access delay (trdram): this field defines the minimum round trip propagation time of the rdram channel in units of rdram clo cks (rclks). this value incl udes the cas access time, the channel delay time, or any mrh delay time. trdram = tcac + trdly ? trdram has a minimum value of 8 rclks since the supported rdram tcac = 8 rclks. ? the maximum value of trdram is 12 rclks in single channel-pair mode. ? the maximum value of trdram is 24 rclks in multiple channel-pair mode.. ? trdly is the total channel delay time and should include the channel delay time of the rdram device in the mch rdram interface, the mrh-r propagation delay time, and the channel delay time of the rdram device in the mrh-r rdram interface. the following table shows the valid trcd and tcac combinations for 300 mhz and 400 mhz. rdram frequency (rclk) trcd in rclks tcac in rclks 400 mhz 9 8 400 mhz 7 8 300 mhz 7 8
70 datasheet 3.4.34. rdcr?rdram refresh control register (device 0) address offset: bfh default value: 00h access: read/write size: 8 bits this register is loaded by configuration software with the refresh timings when the direct rdram devices or the mrh-r present bit is set in the ricm register (device 0, offset 94h, bit 24) for all rdram channels present in the system. the value placed into this register should represent the least common denominator of all of the devices on the specified channel pair. the mch starts the refresh cycles after bit 27 (offset 94?97h), initialization complete bit, is programmed by bios. bit description 7:6 dram refresh rate for rdram channel pair #3 (drr3): the dram refresh rate is adjusted according to the frequency selected by this field. note that refresh is also disabled via this field, and that disabling refresh results in the eventual loss of dram data. this field is programmed by bios after collecting configuration information from all direct rdram devices in the channel and determining the least common denominator value for refresh. 00 = refresh disabled 01 = 1.95 us 10 = 3.9 us 11 = 7.8 us 5:4 dram refresh rate rdram channel pair #2 (drr2): the dram refresh rate is adjusted according to the frequency selected by this field. note that refresh is also disabled via this field, and that disabling refresh results in the eventual loss of dram data. this field is programmed by bios after collecting configuration information from all direct rdram devices in the channel and determining the least common denominator value for refresh. 00 = refresh disabled 01 = 1.95 us 10 = 3.9 us 11 = 7.8 us 3:2 dram refresh rate rdram channel pair #1 (drr1): the dram refresh rate is adjusted according to the frequency selected by this field. note that refresh is also disabled via this field, and that disabling refresh results in the eventual loss of dram data. this field is programmed by bios after collecting configuration information from all direct rdram devices in the channel and determining the least common denominator value for refresh. 00 = refresh disabled 01 = 1.95 us 10 = 3.9 us 11 = 7.8 us 1:0 dram refresh rate rdram channel pair #0 (drr0): the dram refresh rate is adjusted according to the frequency selected by this field. note that refresh is also disabled via this field, and that disabling refresh results in the eventual loss of dram data. this field is programmed by bios after collecting config information from all direct rdram devices in the channel and determining the least common denominator value for refresh. 00 = refresh disabled 01 = 1.95 us 10 = 3.9 us 11 = 7.8 us
82840 mch r datasheet 71 3.4.35. tom?top of low memory register (device 0) address offset: c4?c5h default value: 00h access: read/write size: 16 bits a memory hole is present under normal operating conditions from tom up to the 4 gb address where tom is the top of lower memory register. this hole is used to access devices present behind hub interfaces a and b, the agp bus, the memory-mapped apic register, and the boot bios area just below 4 gb. thus, the hole range subtracts from the overall available rdram memory and will effectively break the main memory into two contiguous areas: one below tom and one above 4 gb, if available rdram exceeds 4 gb. if the total amount of main memory is less than 4 gb, the addresses (i.e., not their ?values? ) indicated by the tom and gba15 (or tom and srba7) registers will be identical. bit description 15:0 top of low memory (tom): this register contains the address that corresponds to bits 31:16 of the maximum dram memory address that lies below 4 gb. configuration software should set this value to either the maximum amount of memory in the system or to the minimum address allocated for pci memory or the graphics aperture, whichever is smaller. 3.4.36. errsts?error status register (device 0) address offset: c8?c9h default value: 0000h access: read/write clear size: 16 bits this register is used to report various error conditions via the hub interface messages to ich. an serr, smi, or sci error message may be generated via the hub interface a on a zero to one transition of any of these flags, when enabled in the pcicmd/errcmd, smicmd, or scicmd registers respectively. bit description 15 fsb parity error (fsbpar): 1 = the mch detected an uncorrectable parity error on either the address or request signals of the front side bus. 0 = software must write a 1 to clear this bit. 14 serr request from agp port (agperr): 1 = agp interface has received an serr request from the device 1 virtual bridge. the serr requests include the agp parity error, agp forwarding serr# error, and agp receiving targeted abort error. if the appropriate bit is set in the errcmd register, this request is forwarded down hub interface a to the ich. 0 = software must write a 1 to clear this bit. 13 serr request from hub interface b (hlberr): 1 = hub interface b has received an serr request from the device 2 virtual bridge. the serr requests include the hub interface b parity error and forwarding serr# error. if the appropriate bit is set in the errcmd register, this request is forwarded down hub interface a to the ich. 0 = software must write a 1 to clear this bit.
72 datasheet bit description 12 host uncorrectable error (fsbbierr): 1 = mch detected the assertion of either the berr# signal or the ierr# signal on the processor bus. an serr or sci hub interface a message will be generated to ich, if the appropriate bit is enabled in the errcmd or scicmd register. 0 = software must write a 1 to clear this bit. 11 host correctable error (hcerr): 1 = mch detected a correctable data error on the host bus. an sci or smi hub interface a message will be generated to ich, if the appropriate bit is enabled in the scicmd or smicmd register. 0 = software must write a 1 to clear this bit. 10 external thermal trip (etst): 1 = mch detected a rising edge on the overt# or the rdram devices report an overtemperature conditions. the overt# should be used to receive an interrupt from an external thermal sensor when the sensor has been tripped. an serr, sci or smi hub interface a message will be generated to ich, if the appropriate bit is enabled in the errcmd, scicmd or smicmd register. 0 = software must write a 1 to clear this bit. 9 lock to non-dram memory flag (lckf)?r/wc: 1 = when this bit is set it indicates that a host initiated lock cycle targeting non-dram memory space occurred. 0 = software must write a 1 to clear this bit. 8 serr on hub interface b target abort (tahlb): 1 = mch detected that an mch originated hub interface b cycle is terminated with a target abort. an serr, sci or smi hub interface a message will be generated to ich, if the appropriate bit is enabled in the errcmd, scicmd or smicmd register. 0 = software must write a 1 to clear this bit. 7 unimplemented hub interface b special cycle (unscb): 1 = mch initiated a hub interface b request that was terminated with a unimplemented special cycle completion packet. an serr, sci or smi hub interface a message will be generated to the ich, if the appropriate bit is enabled in the errcmd, scicmd or smicmd register. 0 = software must write a 1 to clear this bit. 6 serr on hub interface a target abort (tahla): 1 = mch detected that an mch originated hub interface a cycle is terminated with a target abort. an serr, sci or smi hub interface a message will be generated to the ich, if the appropriate bit is enabled in the errcmd, scicmd or smicmd register. 0 = software must write a 1 to clear this bit. 5 unimplemented hub interface a special cycle (unsca): 1 = mch initiated a hub interface a request that was terminated with a unimplemented special cycle completion packet. an serr, sci or smi hub interface a message will be generated to the ich, if the appropriate bit is enabled in the errcmd, scicmd or smicmd register. 0 = software must write a 1 to clear this bit. 4 agp access outside of graphics aperture flag (oogf): 1 = indicates that an agp access occurred to an address that is outside of the graphics aperture range. an serr, sci or smi hub interface a message will be generated to the ich, if the appropriate bit is enabled in the errcmd, scicmd or smicmd register. 0 = software must write a 1 to clear this bit.
82840 mch r datasheet 73 bit description 3 invalid agp access flag (iaaf): 1 = an agp access was attempted outside of the graphics aperture and either to the 640 kb ? 1 mb range or above the top of memory. an serr, sci or smi hub interface a message will be generated to the ich, if the appropriate bit is enabled in the errcmd, scicmd or smicmd register. 0 = software must write a 1 to clear this bit. 2 invalid graphics aperture translation table entry (ittef): 1 = an invalid translation table entry was returned in response to an agp access to the graphics aperture. an serr, sci or smi hub interface a message will be generated to the ich, if the appropriate bit is enabled in the errcmd, scicmd or smicmd register. 0 = software must write a 1 to clear this bit. 1 multiple-bit dram ecc error flag (dmerr): 1 = a memory read data transfer had an uncorrectable multiple-bit error. when this bit is set, the address that caused the error and the syndrome are logged in the eap register. once this bit is set, the eap field in the error address pointer register and the deccsyn field in the dram error control/status register are locked until the processor clears this bit by writing a 1. software uses bits [1:0] to detect whether the logged error address is for single or multiple-bit error. 0 = once software completes the error processing, a value of 1 is written to this bit to clear the value (back to 0) and unlock the error logging mechanism. 0 single-bit dram ecc error flag (dserr): 1 = a memory read data transfer had a single-bit correctable error and the corrected data was sent for the access. when this bit is set, the address that caused the error and the syndrome are logged in the eap register. once this bit is set, the eap field in the error address pointer register register and the deccsyn field in the dram error control/status register are locked to prevent further single bit error updates until the processor clears this bit by writing a 1. a multiple bit error that occurs after this bit is set will overwrite the eap field with the multiple bit error address; the dcerr or ducerr bits in the dram error control/status register will also be set. 0 = software must write a 1 to clear this bit and unlock the error logging mechanism. 3.4.37. errcmd?error command register (device 0) address offset: ca?cbh default value: 0000h access: read/write size: 16 bits this register enables various errors to generate a serr message via the hub interface a. since the mch does not have an serr# signal, serr messages are passed from the mch to the ich over the hub interface. note: the actual generation of the serr message is globally enabled for device 0 via the pci command register. note: an error can generate one and only one error message via the hub interface a. it is software?s responsibility to make sure that when an serr error message is enabled for an error condition, smi and sci error messages are disabled for that same error condition.
74 datasheet bit description 15 serr on host bus error enable (hbserr): 1 = enable. generation of the hub interface a serr message is enabled for the parity errors on the address or request signals of the front side bus. 0 = disable 14 agp serr enable (agpserr): 1 = enable. the generation of the hub interface a serr message is enabled for the agp parity error, serr# or target abort if the appropriate bit is enabled in th device 1 register. 0 = disable. agp serr events are ignored. 13 serr request from hub interface b (hlbserr): 1 = enable. the generation of the hub interface a serr message is enabled for the receipt of an serr request from the hub interface b. 0 = disable 12 serr on host uncorrectable error (hucserr): 1 = enable. the generation of the hub interface a serr message is enabled when the mch detects the berr# or the ierr# error condition on the front side bus. 0 = disable 11 reserved 10 serr on external thermal sensor trip (therm_serr): 1 = enable. the generation of the hub interface a serr message is enabled when the mch has detected a rising edge on the overt# or the rdram devices report an overtemperature conditions. 0 = disable. 9 reserved 8 serr on target abort on hub interface b exception (tahlb_serr): 1 = enable. the generation of the hub interface a serr message is enabled when an mch originated hub interface b cycle is completed with "target abort" status. 0 = disable 7 serr on hub interface b unimplemented special cycle (unscb_serr): 1 = enable. when this bit is set, the generation of the hub interface a serr message is enabled when an mch initiated hub interface b request is terminated with a unimplemented special cycle completion packet. 0 = disable 6 serr on target abort on hub interface a exception (tahla_serr): 1 = enable. the generation of the hub interface a serr message is enabled when an mch originated hub interface a cycle is completed with "target abort" status. 0 = disable 5 serr on hub interface a unimplemented special cycle (unsca_serr): 1 = enable. the generation of the hub interface a serr message is enabled when an mch initiated hub interface a request is terminated with a unimplemented special cycle completion packet. 0 = disable
82840 mch r datasheet 75 bit description 4 serr on agp access outside of graphics aperture (oogf_serr) 1 = enable. the generation of the hub interface a serr message is enabled when an agp access occurs to an address outside of the graphics aperture. 0 = disable 3 serr on invalid agp access (iaaf_serr) 1 = enable. the generation of the hub interface a serr message is enabled when an agp access occurs to an address outside of the graphics aperture and either to the 640 kb ? 1 mb range or above the top of memory. 0 = disable 2 serr on invalid translation table entry (ittef_serr) : 1 = enable. the generation of the hub interface a serr message is enabled when an invalid translation table entry was returned in response to an agp access to the graphics aperture. 0 = disable 1 serr multiple-bit dram ecc error (dmerr_serr): 1 = enable. the generation of the hub interface a serr message is enabled when the mch dram controller detects a multiple-bit error. for systems not supporting ecc, this bit must be disabled. 0 = disable 0 serr on single-bit ecc error (dserr): 1 = enable. when this bit is set, the generation of the hub interface a serr message is enabled when the mch dram controller detects a single bit error. for systems not supporting ecc, this bit must be disabled. 0 = disable 3.4.38. smicmd?smi command register (device 0) address offset: cc?cdh default value: 0000h access: read/write size: 16 bits this register enables various errors to generate a smi message via the hub interface a. note: an error can generate one and only one error message via the hub interface a. it is software?s responsibility to make sure that when an smi error message is enabled for an error condition, serr and sci error messages are disabled for that same error condition. bit description 15:12 reserved 11 smi on host correctable error (hcsmi): 1 = enable. when this bit is set, the generation of the hub interface a smi message is enabled when the mch has detected a correctable single-bit data error on the host bus. 0 = disable. this bit must be set to a 0 if the systems does not implement the data correction on the host bus.
76 datasheet bit description 10 smi on external thermal sensor trip (therm_smi): 1 = when this bit is set, the generation of the hub interface a smi message is enabled when the mch has detected a rising edge on the overt# or the rdram devices report an overtemperature conditions. 0 = disable 9 reserved 8 smi on target abort on hub interface b exception (tahlb_smi): 1 = enable. the generation of the hub interface a smi message is enabled when an mch originated hub interface b cycle is completed with "target abort" status. 0 = disable. 7 smi on hub interface b unimplemented special cycle (unscb_smi): 1 = enable. the generation of the hub interface a smi message is enabled when an mch initiated hub interface b request is terminated with a unimplemented special cycle completion packet. 0 = disable. 6 smi on target abort on hub interface a exception (tahla_smi): 1 = enable. the generation of the hub interface a smi message is enabled when an mch originated hub interface a cycle is completed with "target abort" status. 0 = disable 5 smi on hub interface a unimplemented special cycle (unsca_smi): 1 = enable. the generation of the hub interface a smi message is enabled when an mch initiated hub interface a request is terminated with a unimplemented special cycle completion packet. 0 = disable 4 smi on agp access outside of graphics aperture (oogf_smi) : 1 = enable. the generation of the hub interface a smi message is enabled when an agp access occurs to an address outside of the graphics aperture. 0 = disable. 3 smi on invalid agp access (iaaf_smi): 1 = enable. the generation of the hub interface a smi message is enabled when an agp access occurs to an address outside of the graphics aperture and either to the 640 kb ? 1 mb range or above the top of memory. 0 = disable. 2 smi on invalid translation table entry (ittef_smi): 1 = enable. when this bit is set, the generation of the hub interface a smi message is enabled when an invalid translation table entry was returned in response to an agp access to the graphics aperture. 0 = disable. 1 smi on multiple-bit dram ecc error (dmerr_smi): 1 = enable. the generation of the hub interface a smi message is enabled when the mch dram controller detects a multiple-bit error. 0 = disable. for systems not supporting ecc this bit must be disabled. 0 smi on single-bit ecc error (dserr_smi): 1 = tthe generation of the hub interface a smi message is enabled when the mch dram controller detects a single bit error. 0 = disable. for systems that do not support ecc, this bit must be disabled.
82840 mch r datasheet 77 3.4.39. scicmd?sci command register (device 0) address offset: ce?cfh default value: 0000h access: read/write size: 16 bits this register enables various errors to generate a sci message via the hub interface a. note: an error can generate one and only one error message via the hub interface a. it is software?s responsibility to make sure that when an sci error message is enabled for an error condition, serr and smi error messages are disabled for that same error condition. bit description 15:13 reserved 12 sci on host uncorrectable error (hucsci): 1 = enable. the generation of the hub interface a sci message is enabled when the mch detects the berr# or the ierr# error condition on the front side bus. 0 = disable. 11 sci on host correctable error (hcsci): 1 = enable. the generation of the hub interface a sci message is enabled when the mch has detected a correctable single-bit data error on the host bus. 0 = disable. this bit must be set to a 0 if the systems does not implement the data correction on the host bus. 10 sci on external thermal sensor trip (therm_sci): 1 = enable. the generation of the hub interface a sci message is enabled when the mch has detected a rising edge on the overt# or the rdram devices report an overtemperature conditions. 0 = disable. 9 sci on lock to non-dram memory flag (lckf_sci): 1 = enable. the generation of the hub interface a sci message is enabled when a host initiated lock cycle targeting non-dram memory space has occurred. 0 = disable. if this bit is set to ?0?, then the reporting of this condition is disabled. 8 sci on target abort on hub interface b exception (tahlb_sci): 1 = enable. the generation of the hub interface a sci message is enabled when an mch originated hub interface b cycle is completed with "target abort" status. 0 = disable. 7 sci on hub interface b unimplemented special cycle (unscb_sci): 1 = enable. the generation of the hub interface a sci message is enabled when an mch initiated hub interface b request is terminated with a unimplemented special cycle completion packet. 0 = disable. 6 sci on target abort on hub interface a exception (tahla_sci): 1 = enable. the generation of the hub interface a sci message is enabled when an mch originated hub interface a cycle is completed with "target abort" status. 0 = disable. 5 sci on hub interface a unimplemented special cycle (unsca_sci): 1 = enable. the generation of the hub interface a sci message is enabled when an mch initiated hub interface a request is terminated with a unimplemented special cycle completion packet. 0 = disable.
78 datasheet bit description 4 sci on agp access outside of graphics aperture (oogf_sci): 1 = enable. the generation of the hub interface a sci message is enabled when an agp access occurs to an address outside of the graphics aperture. 0 = disable. 3 sci on invalid agp access (iaaf_sci): 1 = enable. the generation of the hub interface a sci message is enabled when an agp access occurs to an address outside of the graphics aperture and either to the 640 kb ? 1 mb range or above the top of memory. 0 = disable. 2 sci on invalid translation table entry (ittef_sci): 1 = enable. the generation of the hub interface a sci message is enabled when an invalid translation table entry was returned in response to an agp access to the graphics aperture. 0 = disable. 1 sci on multiple-bit dram ecc error (dmerr_sci): 1 = enable. the generation of the hub interface a sci message is enabled when the mch dram controller detects a multiple-bit error. 0 = disable. for systems not supporting ecc, this bit must be disabled. 0 sci on single-bit ecc error (dserr_sci): 1 = enable. the generation of the hub interface a sci message is enabled when the mch dram controller detects a single bit error. 0 = disable. for systems that do not support ecc, this bit must be disabled. 3.4.40. skpd?scratchpad data (device 0) address offset: de?dfh default value: 0000h access: read/write size: 16 bits bit description 15:0 scratchpad [15:0]: these bits are simply r/w storage bits that have no effect on the mch functionality.
82840 mch r datasheet 79 3.4.41. herrctl_sts?host error control/status register (device 0) address offset: e0?e1h default value: 0000h access: read/write, read/write clear size: 16 bits this register enables and reflects the status of various errors checking functions which the mch supports on the front side bus. bit description 15 detected berr (dberr)?r/wc: 1 = mch detected a berr# error condition on the host bus. 0 = software must write a 1 to this field to clear it. 14 detected ierr (dierr)?r/wc: 1 = mch detected an ierr# error condition on the host bus. 0 = software must write a 1 to this field to clear it. 13:12 reserved 11 host bus berr# and ierr# enable (bierren)?r/w: 1 = enable. the detection of either a berr or an ierr signal on the host bus is enabled. the type of message sent is controlled by the errcmd, scicmd, and smicmd registers. 0 = disable. 10 host bus multiple bit error (hucerr )? r/wc: 1 = mch detected an uncorrectable error on the host bus. 0 = software must write a 1 to this bit to clear it. 9 host bus berr# enable (hucberr)?r/w: 1 = enable. generation of the host bus berr signal when the mch detects an uncorrectable error on the host bus data pins is enabled. 0 = disable. 8 host bus ecc generation strapping status (heccss)?ro: this bit reflects the status of the mch strapping option of enabling the error correcting codes generation for host bus transactions. 1 = enable (via strapping option) 0 = disable (via strapping option) 7:0 host bus ecc syndrome (heccsyn)?ro: after a host bus ecc error, hardware loads this field with a syndrome that describes the set of bits found to be in error. note that this field is locked from the time that it is loaded to the time when it is read by software. if the first error was a single bit, correctable error, then a subsequent multiple bit error will overwrite this field. in all other cases, an error which occurs after the first error and before the register has been read by software will escape recording.
80 datasheet 3.4.42. derrctl_sts?dram error control/status register (device 0) address offset: e2?e3h default value: 0000h access: read only, read/write clear size: 16 bits this register enables and reflects the status of various errors checking functions which the mch supports on the dram interface. bit description 15:12 reserved 11 dram correctable ecc error (dcerr )? r/wc: 1 = mch detected a correctable error on the dram interface. 0 = it is cleared by writing 1 to it or when an uncorrectable error is detected on the bus. 10 dram multiple bit error (ducerr)?r/wc: 1 = mch detected an uncorrectable error on the dram interface. 0 = it is cleared by writing 1 to it. 9:8 reserved 7:0 dram ecc syndrome (deccsyn)?ro: after a dram ecc error, hardware loads this field with a syndrome that describes the set of bits found to be in error. note that this field is locked from the time that it is loaded up to the time when it is read by software. if the first error was a single bit, correctable error, then a subsequent multiple bit error will overwrite this field. in all other cases, an error which occurs after the first error and before the register has been read by software will escape recording. 3.4.43. eap?error address pointer register (device 0) address offset: e4?e7h default value: 0000h access: read only size: 32 bits this register stores the dram address when an ecc error occurs. bit description 31:11 error address pointer (eap)?ro: this field is used to store the 4 kb block of main memory where an error (single bit or multi-bit error) has occurred. note that the value of this bit field represents the address of the first single or the first multiple bit error occurrence after the error flag bits in the errsts register have been cleared by software. a multiple bit error will overwrite a single bit error. once the error flag bits are set as a result of an error, this bit field is locked and doesn't change as a result of a new error. 10:1 reserved 0 error address segment (eas)?ro: this bit indicates whether the reported error was found on rambus* channel 0 or on channel 1. 1 = channel 1 0 = channel 0
82840 mch r datasheet 81 3.4.44. agpbctrl?agp buffer strength control register address offset: e8?ebh default value: 0000h access: read/write size: 32 bits this register controls the 3.3v agp buffer strength. the proper setting is documented in the intel ? 840 bios specification update . bit description 31:24 agp buffer strength control 1: 23:16 agp buffer strength control 2:. 15:0 reserved 3.4.45. agpappend?agp append disable register address offset: f6h default value: 00h access: read/write size: 8 bits this register controls the agp interface. bit description 7:6 reserved 5 agp append disable: 1 = disable cpu-to-agp write appending 0 = enable (default). 4:0 reserved 3.4.46. gtlnclamp?gtl n clamp disable register address offset: f7h default value: 00h access: read/write size: 8 bits bit description 7 reserved 6:5 gtl n-clamp disable register: 10 = disable. 4:0 reserved
82 datasheet 3.5. agp bridge registers (device 1) table 5 summarizes the mch configuration space for device 1. table 5. mch configuration space (device 1) address offset symbol register name default value access 00?01h vid1 vendor identification 8086h ro 02?03h did1 device identification 1a23h ro 04?05h pcicmd1 pci command register 0000h r/w 06?07h pcists1 pci status register 0020h ro, r/wc 08 rid1 revision identification 00h ro 09 ? reserved 00h ? 0ah subc1 sub-class code 04h ro 0bh bcc1 base class code 06h ro 0ch ? reserved 00h ? 0dh mlt1 master latency timer 00h r/w 0eh hdr1 header type 01h ro 0f?17h ? reserved 00h ? 18h pbusn1 primary bus number 00h ro 19h sbusn1 secondary bus number f0h r/w 1ah subusn1 subordinate bus number 00h r/w 1bh smlt1 secondary bus master latency timer 00h r/w 1ch iobase1 i/o base address register 00h r/w 1dh iolimit1 i/o limit address register 00h r/w 1e?1fh ssts1 secondary status register 02a0h ro, r/wc 20?21h mbase1 memory base address register fff0h r/w 22?23h mlimit1 memory limit address register 0000h r/w 24?25h pmbase1 prefetchable memory base address reg. fff0h r/w 26?27h pmlimit1 prefetchable memory limit address reg. 0000h r/w 28?3dh ? reserved ? ? 3eh bctrl1 bridge control register 00h r/w 3fh ? reserved ? ? 40h errcmd1 error command 00h r/w 41?ffh ? reserved ? ?
82840 mch r datasheet 83 3.5.1. vid1?vendor identification register (device 1) address offset: 00?01h default value: 8086h attribute: read only size: 16 bits the vid register contains the vendor identification number. this 16-bit register combined with the device identification register uniquely identify any pci device. writes to this register have no effect. bit description 15:0 vendor identification number: this is a 16-bit value assigned to intel. intel vid = 8086h. 3.5.2. did1?device identification register (device 1) address offset: 02?03h default value: 1a23h attribute: read only size: 16 bits this 16-bit register combined with the vendor identification register uniquely identifies any pci device. writes to this register have no effect. bit description 15:0 device identification number: this is a 16 bit value assigned to the mch device 1. the mch device 1 did = 1a23h.
84 datasheet 3.5.3. pcicmd1?pci-pci command register (device 1) address offset: 04?05h default: 0000h access: read only, read/write size 16 bits bit descriptions 15:10 reserved 9 fast back-to-back?ro: (not applicable). hardwired to 0. 8 serr message enable (serre1)?r/w . this bit is a global enable bit for device 1 serr messaging. the mch does not have an serr# signal. the mch communicates the serr# condition by sending an serr message to the ich. 1 = enable. the mch is enabled to generate serr messages over the hub interface for specific device 1 error conditions that are individually enabled in the bctrl register. the error status is reported in the pcists1 register. 0 = disable. the serr message is not generated by the mch for device 1. note: this bit only controls serr messaging for the device 1. device 0 has its own serre bit to control error reporting for error conditions occurring on device 0. 7 address/data stepping?ro: (not applicable). hardwired to 0. 6 parity error enable (perre1)? ro: perr# is not supported on agp. hardwired to 0. 5 reserved 4 memory write and invalidate enable?ro: (not implemented). hardwired to 0. 3 special cycle enable?ro: (not implemented). hardwired to 0. 2 bus master enable (bme1)? r/w: 1 = enable. agp master initiated frame# cycles will be accepted by the mch, if they hit a valid address decode range. 0 = disable (default). agp master initiated frame# cycles will be ignored by the mch resulting in a master abort. note that incoming configuration cycles still need to be accepted regardless of the setting of this bus master enable bit. this bit has no affect on agp master originated sba or pipe# cycles. 1 memory access enable (mae1)?r/w: 1 = enable. this bit must be 1 to enable the memory and prefetchable memory address ranges defined in the mbase1, mlimit1, pmbase1, and pmlimit1 registers. 0 = disable. all of device 1?s memory space is disabled. 0 i/o access enable (ioae1)? r/w: this bit must be set to1 to enable the i/o address range defined in the iobase1, and iolimit1 registers. when set to 0 all of device 1?s i/o space is disabled.
82840 mch r datasheet 85 3.5.4. pcists1?pci-pci status register (device 1) address offset: 06?07h default value: 0000h access: read only, read/write clear size: 16 bits pcists1 is a 16-bit status register that reports the occurrence of error conditions associated with the primary side of the ?virtual? pci-pci bridge in the mch. since this device does not physically reside on pci_a, it reports the optimum operating conditions so that it does not restrict the capability of pci_a. bit descriptions 15 detected parity error (dpe1)?ro: (not applicable). hardwired to 0. 14 signaled system error (sse1)?r/wc: 1 = mch device 1 generates an serr message over the hub interface a for any enabled device 1 error condition. device 1 error conditions are enabled in the pcicmd1 and bctrl1 registers. device 1 error flags are read/reset from the ssts1 register. 0 = software clears this bit by writing a 1 to it. 13 received master abort status (rmas1)? ro: (not applicable). hardwired to 0. 12 received target abort status (rtas1) ?ro: (not applicable). hardwired to 0. 11 signaled target abort status (stas1) (ro): (not applicable). hardwired to 0. 10:9 devsel# timing (devt1): this bit field is hardwired to ?00b? to indicate that the device 1 uses the fastest possible decode. 8 data parity detected (dpd1)?ro: parity is not supported on agp port. hardwired to 0. 7 fast back-to-back (fb2b1)?ro: agp port always supports fast back to back transactions. hardwired to 1. 6 reserved. 5 33/66 mhz capability?ro: agp port is 66 mhz capable. hardwired to 1. 4:0 reserved. 3.5.5. rid1?revision identification register (device 1) address offset: 08h default value: 00h access: read only size: 8 bits this register contains the revision number of the mch device 1. these bits are read only and writes to this register have no effect. for the a-0 stepping, this value is 00h. bit description 7:0 revision identification number: this is an 8-bit value that indicates the revision identification number for the mch device 1.
86 datasheet 3.5.6. subc1?sub-class code register (device 1) address offset: 0ah default value: 04h access: read only size: 8 bits this register contains the sub-class code for the mch device 1. bit description 7:0 sub-class code (subc1): this is an 8-bit value that indicates the category of bridge for the mch. 04h = pci-to-pci bridge. 3.5.7. bcc1?base class code register (device 1) address offset: 0bh default value: 06h access: read only size: 8 bits this register contains the base class code of the mch device 1. bit description 7:0 base class code (basec): this is an 8-bit value that indicates the base class code for the mch device 1. 06h = bridge device. 3.5.8. mlt1?master latency timer register (device 1) address offset: 0dh default value: 00h access: read/write size: 8 bits this functionality is not applicable. it is described here since these bits should be implemented as a read/write to prevent standard pci-pci bridge configuration software from getting ?confused? . bit description 7:3 not applicable but support read/write operations. (reads return previously written data.) 2:0 reserved. 3.5.9. hdr1?header type register (device 1) offset: 0eh default: 01h access: read only size: 8 bits this register identifies the header layout of the configuration space. bit descriptions 7:0 header type: hardwired to 01h.
82840 mch r datasheet 87 3.5.10. pbusn1?primary bus number register (device 1) offset: 18h default: 00h access: read only size: 8 bits this register identifies that ?virtual? pci-pci bridge is connected to bus #0. bit descriptions 7:0 primary bus number: hardwired to 00h. 3.5.11. sbusn1?secondary bus number register (device 1) offset: 19h default: 00h access: read /write size: 8 bits this register identifies the bus number assigned to the second bus side of the ?virtual? pci-pci bridge (i.e., to agp). this number is programmed by the pci configuration software to allow mapping of configuration cycles to agp. bit descriptions 7:0 secondary bus number: programmable. default=00h. 3.5.12. subusn1?subordinate bus number register (device 1) offset: 1ah default: 00h access: read /write size: 8 bits this register identifies the subordinate bus (if any) that resides at the level below agp. this number is programmed by the pci configuration software to allow mapping of configuration cycles to agp. bit descriptions 7:0 subordinate bus number: programmable. default = 0.
88 datasheet 3.5.13. smlt1?secondary master latency timer register (device 1) address offset: 1bh default value: 00h access: read/write size: 8 bits this register controls the bus tenure of the mch on agp. smlt1 controls the amount of time the mch, as a agp/pci bus master, can burst data on the agp bus. the count value is an 8 bit quantity; however, mlt[2:0] are reserved and assumed to be 0 when determining the count value. the smlt1 is used to guarantee to the agp master a minimum amount of the system resources. when the mch begins the first agp frame# cycle after being granted the bus, the counter is loaded and enabled to count from the assertion of frame#. if the count expires while the mch?s grant is removed (due to agp master request), the mch loses the use of the bus, and the agp master agent may be granted the bus. if the mch?s bus grant is not removed, the mch continues to own the agp bus, regardless of the smlt1 expiration or idle condition. note that the mch must always properly terminate an agp transaction, with frame# negation prior to the final data transfer. the number of clocks programmed in the smlt1 represents the guaranteed time slice (measured in 66 mhz agp clocks) allotted to the mch, after which it must complete the current data transfer phase and then surrender the bus as soon as its bus grant is removed. for example, if the smlt1 is programmed to 18h, then the value is 24 agp clocks. the default value of 00h disables this function. when the smlt1 is disabled, the burst time for the mch is unlimited (i.e., the mch can burst forever). bit description 7:3 secondary mlt counter value: default=0 (i.e., smlt1 disabled) 2:0 reserved. 3.5.14. iobase1?i/o base address register (device 1) address offset: 1ch default value: f0h access: read/write size: 8 bits this register control the host to agp i/o access routing based on the following formula: io_base address io_limit only the upper 4 bits are programmable. for the purpose of address decode, address bits a[11:0] are treated as 0. thus, the bottom of the defined i/o address range will be aligned to a 4 kb boundary. note: bios must not set this register to 00h; otherwise, 0cf8h/0cfch accesses will be forwarded to agp. bit description 7:4 i/o address base: corresponds to a[15:12] of the i/o address. default=f0h 3:0 reserved.
82840 mch r datasheet 89 3.5.15. iolimit1?i/o limit address register (device 1) address offset: 1dh default value: 00h access: read/write size: 8 bits this register controls the host to agp i/o access routing based on the following formula: io_base address io_limit only the upper 4 bits are programmable. for the purpose of address decode, address bits a[11:0] are assumed to be fffh. thus, the top of the defined i/o address range will be at the top of a 4 kb aligned address block. bit description 7:4 i/o address limit: corresponds to a[15:12] of the i/o address. default=0 3:0 reserved. (only 16 bit addressing supported.) 3.5.16. ssts1?secondary pci-pci status register (device 1) address offset: 1e?1fh default value: 02a0h access: read only, read/write clear size: 16 bits ssts is a 16-bit status register that reports the occurrence of error conditions associated with the secondary side (i.e., agp side ) of the ?virtual? pci-pci bridge in the mch. bit descriptions 15 detected parity error (dpe1)?r/wc: 1 = mch detected a parity error in the address or data phase of agp bus transactions. 0 = software sets dpe1 to 0 by writing a 1 to this bit. note that the function of this bit is not affected by the perre1 bit. also note that perr# is not implemented in the mch. 14 received system error (sse1)?r/wc: 1 = mch generates an serr message for any enabled error condition under device 1. device 1 error conditions are enabled in the bctrl1 register. 0 = software clears sse1 to 0 by writing a 1 to this bit. 13 received master abort status (rmas1)?r/wc: 1 = mch terminates a host-to-agp with an unexpected master abort. 0 = software resets this bit to 0 by writing a 1 to it. 12 received target abort status (rtas1)?r/wc: 1 = mch-initiated transaction on agp is terminated with a target abort. 0 = software resets rtas1 to 0 by writing a 1 to it.
90 datasheet bit descriptions 11 signaled target abort status (stas1)?ro: mch does not generate target abort on agp. hardwired to a 0. 10:9 devsel# timing (devt1)?ro: this 2-bit field indicates the timing of the devsel# signal when the mch responds as a target on agp, and is hardwired to the value 01b (medium) to indicate the time when a valid devsel# can be sampled by the initiator of the pci cycle. 8 data parity detected (dpd1)?ro: (not implemented): hardwired to 0. mch does not implement g_perr# function. however, data parity errors are still detected and reported via the hub interface a (if enabled by serre1 bit of the pcicmd1 register and bit 0 of the bctrl register). 7 fast back-to-back (fb2b1)?ro: mch, as a target, supports fast back-to-back transactions on agp. hardwired to 1. 6 reserved 5 33/66 mhz capable (cap66)?ro: agp bus is capable of 66 mhz operation. hardwired to 1. 4:0 reserved. 3.5.17. mbase1?memory base address register (device 1) address offset: 20?21h default value: fff0h access: read/write size: 16 bits this register controls the host to agp non-prefetchable memory access routing based on the following formula: memory_base1 address memory_limit1 the upper 12 bits of this register are read/write and correspond to the upper 12 address bits a[31:20] of the 32 bit address. the lower 4 bits of this register are read-only and return zeroes when read. this register must be initialized by configuration software. for the purpose of address decode, address bits a[19:0] are assumed to be 0. thus, the bottom of the defined memory address range will be aligned to a 1 mb boundary. bit description 15: 4 memory address base 1 (mem_base1): corresponds to a[31:20] of the memory address. 3:0 reserved.
82840 mch r datasheet 91 3.5.18. mlimit1?memory limit address register (device 1) address offset: 22?23h default value: 0000h access: read/write size: 16 bits this register controls the host to agp non-prefetchable memory access routing based on the following formula: memory_base1 address memory_limit1 the upper 12 bits of the register are read/write and correspond to the upper 12 address bits a[31:20] of the 32 bit address. the lower 4 bits of this register are read-only and return zeroes when read. this register must be initialized by the configuration software. for the purpose of address decode, address bits a[19:0] are assumed to be fffffh. thus, the top of the defined memory address range will be at the top of a 1 mb aligned memory block. bit description 15: 4 memory address limit 1(mem_limit1): corresponds to a[31:20] of the memory address. default=0 3:0 reserved. note: memory range covered by mbase1 and mlimit1 registers are used to map non-prefetchable agp address ranges (typically, where control/status memory-mapped i/o data structures of the graphics controller will reside) and pmbase 1and pmlimit1 are used to map prefetchable address ranges (typically, graphics local memory). this segregation allows application of uswc space attribute to be performed in a true plug-and-play manner to the prefetchable address range for improved host-agp memory access performance. 3.5.19. pmbase1?prefetchable memory base address register (device 1) address offset: 24?25h default value: fff0h access: read/write size: 16 bits this register controls the host to agp prefetchable memory accesses routing based on the following formula: prefetchable_memory_base1 address prefetchable_memory_limit1 the upper 12 bits of the register are read/write and correspond to the upper 12 address bits a[31:20] of the 32 bit address. the lower 4 bits of this register are read-only and return zeroes when read. this register must be initialized by the configuration software. for the purpose of address decode, address bits a[19:0] are assumed to be 0. thus, the bottom of the defined memory address range will be aligned to a 1 mb boundary. bit description 15: 4 prefetchable memory address base 1(pmem_base1): corresponds to a[31:20] of the memory address. 3:0 reserved.
92 datasheet 3.5.20. pmlimit1?prefetchable memory limit address register (device 1) address offset: 26?27h default value: 0000h access: read/write size: 16 bits this register controls the host to agp prefetchable memory accesses routing based on the following formula: prefetchable_memory_base1 address prefetchable_memory_limit1 the upper 12 bits of the register are read/write and correspond to the upper 12 address bits a[31:20] of the 32 bit address. the lower 4 bits of this register are read-only and return zeroes when read. this register must be initialized by the configuration software. for the purpose of address decode, address bits a[19:0] are assumed to be fffffh. thus, the top of the defined memory address range will be at the top of a 1 mb aligned memory block. note: a prefetchable memory range is supported to allow segregation by the configuration software between the memory ranges that must be defined as uc and the ones that can be designated as a uswc (i.e., prefetchable) from the processor perspective . bit description 15: 4 prefetchable memory address limit 1(pmem_limit1): corresponds to a[31:20] of the memory address. default=0 3:0 reserved. 3.5.21. bctrl1?pci-pci bridge control register (device 1) address offset: 3eh default: 00h access: read only, read/write size 8 bits this register provides extensions to the pcicmd1 register that are specific to pci-pci bridges. the bctrl provides additional control for the secondary interface (i.e., agp) as well as some bits that affect the overall behavior of the ?virtual? pci-pci bridge embedded within mch (e.g., vga compatible address ranges mapping).
82840 mch r datasheet 93 bit descriptions 7 fast back to back enable?ro: since there is only one target allowed on agp this bit is meaningless.hardwired to 0. the mch will not generate fb2b cycles in 1x mode, but will generate fb2b cycles in 2x and 4x fast write modes. 6 secondary bus reset?ro: mch does not support generation of reset via this bit on the agp. hardwired to 0. note that the only way to perform a hard reset of the agp is via the system reset either initiated by software or hardware via ich. 5 master abort mode?ro: hardwired to 0. this means when acting as a master on agp the mch will discard data on writes and return all 1s during reads when a master abort occurs. 4 reserved 3 vga enable (vgaen1)?r/w: controls the routing of host, hub interface a, and hub interface b initiated transactions targeting vga compatible i/o and memory address ranges. 1 = enable. mch forwards the following host accesses to the agp: ? memory accesses in the range 0a0000h?0bffffh ? i/o addresses where a[9:0] are in the ranges 3b0h?3bbh and 3c0h?3dfh (inclusive of isa address aliases; a[15:10] are not decoded) when enabled, forwarding of these accesses issued by the host is independent of the i/o address and memory address ranges defined by the previously defined base and limit registers. forwarding of these accesses is also independent of the settings of bit 2 (isa enable) of this register, if this bit is 1. 0 = disable. vga compatible memory and i/o range accesses are not forwarded to agp; rather, they are mapped to primary pci unless they are mapped to agp via i/o and memory range registers defined above (iobase1, iolimit1, mbase1, mlimit1, pmbase1, pmlimit1) refer to the system address map chapter for further information. 2 isa enable ?r/w: modifies the response by the mch to an i/o access issued by the host that targets isa i/o addresses. this applies only to i/o addresses that are enabled by the iobase and iolimit registers. 1 = mch will not forward to agp any i/o transactions addressing the last 768 bytes in each 1 kb block, even if the addresses are within the range defined by the iobase and iolimit registers. instead of going to agp these cycles are forwarded to pci0 where they can be subtractively or positively claimed by the isa bridge. 0 = disable (default). all addresses defined by the iobase and iolimit for host i/o transactions are mapped to agp. 1 serr# enable (serre)?r/w: this bit controls the forwarding of serr# on the secondary interface to the primary interface. 1= enable serre. mch generates serr messages to hub interface a when the serr# pin on agp bus is asserted and when the messages are enabled by the serre1 bit in the pcicmd1 register. 0 = disable. 0 parity error response enable?r/w: controls mch?s response to data phase parity errors on agp. note that g_perr# is not implemented by the mch. 1 = address and data parity errors on agp are reported via serr# mechanism, if enabled by serre1 and serre. 0 = address and data parity errors on agp are not reported via the mch serr# signal. other types of error conditions can still be signaled via serr# independent of this bit?s state.
94 datasheet 3.5.22. errcmd1?error command register (device 1) address offset: 40h default value: 00h access: read/write size: 8 bits bit description 7:1 reserved 0 serr on receiving target abort (serta): 1 = mch generates an serr message over hub interface a upon receiving a target abort on agp. 0 = mch does not assert an serr message upon receipt of a target abort on agp. serr messaging for device 1 is globally enabled in the pcicmd1 register.
82840 mch r datasheet 95 3.6. hub interface b bridge registers (device 2) table 6 summarizes the mch configuration space for device 2. table 6. mch configuration space (device 2) address offset symbol register name default access 00?01h vid2 vendor identification 8086h ro 02?03h did2 device identification 1a24h ro 04?05h pcicmd2 pci command register 0000h r/w 06?07h pcists2 pci status register 0020h ro, r/wc 08 rid2 revision identification 00h ro 09 ? reserved 00h ? 0ah subc2 sub-class code 04h ro 0bh bcc2 base class code 06h ro 0ch ? reserved 00h ? 0dh mlt2 master latency timer 00h r/w 0eh hdr2 header type 01h ro 0f?17h ? reserved 00h ? 18h pbusn2 primary bus number 00h ro 19h sbusn2 secondary bus number 00h r/w 1ah subusn2 subordinate bus number 00h r/w 1bh smlt2 secondary bus master latency timer 00h r/w 1ch iobase2 i/o base address register f0h r/w 1dh iolimit2 i/o limit address register 00h r/w 1e?1fh ssts2 secondary status register 02a0h ro, r/wc 20?21h mbase2 memory base address register fff0h r/w 22?23h mlimit2 memory limit address register 0000h r/w 24?25h pmbase2 prefetchable memory base address reg. fff0h r/w 26?27h pmlimit2 prefetchable memory limit address reg. 0000h r/w 28?3dh ? reserved ? ? 3eh bctrl2 bridge control register 00h r/w 3fh ? reserved ? ? 40h errcmd2 error command 00h r/w 41?ffh ? reserved ? ?
96 datasheet 3.6.1. vid2?vendor identification register (device 2) address offset: 00?01h default value: 8086h attribute: read only size: 16 bits the vid register contains the vendor identification number. this 16-bit register combined with the device identification register uniquely identify any pci device. writes to this register have no effect. bit description 15:0 vendor identification number: this is a 16-bit value assigned to intel. intel vid = 8086h. 3.6.2. did2?device identification register (device 2) address offset: 02?03h default value: 1a24h attribute: read only size: 16 bits this 16-bit register combined with the vendor identification register uniquely identifies any pci device. writes to this register have no effect. bit description 15:0 device identification number: this is a 16 bit value assigned to the mch device 2. the mch device 2 did = 1a24h.
82840 mch r datasheet 97 3.6.3. pcicmd2?pci-pci command register (device 2) address offset: 04 ? 05h default: 0000h access: read only, read/write size 16 bits bit descriptions 15:10 reserved. 9 fast back-to-back?ro: (not applicable). hardwired to 0. 8 serr message enable (serre2)?r/w: this bit is a global enable bit for device 2 serr messaging. the mch does not have an serr# signal. the mch communicates the serr# condition by sending an serr message to the ich. 1 = enable. mch is enabled to generate serr messages over the hub interface a for specific device 2 error conditions that are individually enabled in the bctrl2 register. the error status is reported in the pcists2 register. 0 = serr message is not generated by the mch for device 2. note: this bit only controls serr messaging for the device 2. device 0 has its own serre bit to control error reporting for error conditions occurring on device 0. 7 address/data stepping?ro: (not applicable). hardwired to 0. 6 parity error enable (perre2)?r/w: (not applicable). supported as a read/write bit to avoid issues with standard pci-pci bridge configuration software. 5 reserved. 4 memory write and invalidate enable?r/w: (not applicable). supported as a read/write bit to avoid issues with standard pci-pci bridge configuration software. 3 special cycle enable?r/w: (not applicable). supported as a read/write bit to avoid issues with standard pci-pci bridge configuration software. 2 bus master enable (bme2)?r/w: 1 = enable. device#2 (virtual p2p bridge) operates as a master on the primary interface on behalf of a master on the secondary interface for memory or i/o transaction. 0 = disable. device 2 disables response to all memory or i/o transactions on the secondary interface. 1 memory access enable (mae2)?r/w: (not applicable). supported as a read/write bit to avoid issues with standard pci-pci bridge configuration software. 0 i/o access enable (ioae2)?r/w: (not applicable). supported as a read/write bit to avoid issues with standard pci-pci bridge configuration software.
98 datasheet 3.6.4. pcists2?pci-pci status register (device 2) address offset: 06?07h default value: 00a0h access: read only, read/write clear size: 16 bits pcists2 reports the occurrence of error conditions associated with the primary side of the ?virtual? pci- pci bridge in the mch. since this device does not physically reside on pci_a, it reports the optimum operating conditions so that it does not restrict the capability of pci_a. bit descriptions 15 detected parity error (dpe2)?ro: (not applicable). hardwired to 0. 14 signaled system error (sse2)?r/wc: 1 = mch device 2 generates an serr message over the hub interface a for any enabled device 2 error condition. device 2 error conditions are enabled in the pcicmd2 and bctrl2 registers. device 2 error flags are read/reset from the ssts2 register. 0 = software clears this bit by writing a 1 to it. 13 received master abort status (rmas2)?ro: (not applicable). hardwired to 0. 12 received target abort status (rtas2)?ro: (not applicable). hardwired to 0. 11 signaled target abort status (stas2)?ro: (not applicable). hardwired to 0. 10:9 devsel# timing (devt2)?ro: device 2 uses the fastest possible decode. hardwired to 00. 8 data parity detected (dpd2)?ro: (not applicable). hardwired to 0. 7 fast back-to-back (fb2b2)?ro: fast back-to-back writes are always supported. hardwired to 1. 6 reserved. 5 33/66 mhz capability?ro: capable of 66 mhz operation. hardwired to 1. 4:0 reserved. 3.6.5. rid2?revision identification register (device 2) address offset: 08h default value: 00h access: read only size: 8 bits this register contains the revision number of the mch device 2. these bits are read only and writes to this register have no effect. bit description 7:0 revision identification number: this is an 8-bit value that indicates the revision identification number for the mch device 2. a-0 stepping = 00h.
82840 mch r datasheet 99 3.6.6. subc2?sub-class code register (device 2) address offset: 0ah default value: 04h access: read only size: 8 bits this register contains the sub-class code for the mch device 2. bit description 7:0 sub-class code (subc2): this is an 8-bit value that indicates the category of bridge for the mch. 04h = pci-pci bridge. 3.6.7. bcc2?base class code register (device 2) address offset: 0bh default value: 06h access: read only size: 8 bits this register contains the base class code of the mch device 2. bit description 7:0 base class code (basec2): this is an 8-bit value that indicates the base class code for the mch device 2. 06h = bridge device. 3.6.8. mlt2?master latency timer register (device 2) address offset: 0dh default value: 00h access: read/write size: 8 bits this functionality is not applicable. it is described here since these bits should be implemented as a read/write to prevent issues with standard pci-pci bridge configuration software. bit description 7:3 mlt count value: not applicable but support read/write operations. (reads return previously written data.) 2:0 reserved. 3.6.9. hdr2?header type register (device 2) offset: 0eh default: 01h access: read only size: 8 bits this register identifies the header layout of the configuration space. bit descriptions 7:0 header type: this read only field always returns 01h when read. writes have no effect.
100 datasheet 3.6.10. pbusn2?primary bus number register (device 2) offset: 18h default: 00h access: read only size: 8 bits this register identifies that ?virtual? pci-pci bridge is connected to bus #0. bit descriptions 7:0 primary bus number: hardwired to 0. 3.6.11. sbusn2?secondary bus number register (device 2) offset: 19h default: 00h access: read /write size: 8 bits this register identifies the bus number assigned to the second bus side of the ?virtual? pci-pci bridge (the hub interface b connection). this number is programmed by the pci configuration software to allow mapping of configuration cycles to a second bridge device connected to hub interface b. bit descriptions 7:0 secondary bus number: programmable. default=00h. 3.6.12. subusn2?subordinate bus number register (device 2) offset: 1ah default: 00h access: read /write size: 8 bits this register identifies the subordinate bus (if any) that resides at the level below the secondary hub interface. this number is programmed by the pci configuration software to allow mapping of configuration cycles to devices subordinate to the secondary hub interface port. bit descriptions 7:0 subordinate bus number: programmable default = 0. 3.6.13. smlt2?secondary master latency timer register (device 2) address offset: 1bh default value: 00h access: read/write size: 8 bits bit description 7:3 secondary mlt counter value (smlt): default=0 (smlt disabled) 2:0 reserved.
82840 mch r datasheet 101 3.6.14. iobase2?i/o base address register (device 2) address offset: 1ch default value: f0h access: read/write size: 8 bits this register controls the host to hub interface b i/o access routing based on the following formula: io_base2 address io_limit2 only the upper 4 bits are programmable. for the purpose of address decode, address bits a[11:0] are treated as 0. thus, the bottom of the defined i/o address range will be aligned to a 4 kb boundary. bit description 7:4 i/o address base 2: corresponds to a[15:12] of the i/o addresses passed by the device 2 bridge to hub interface b. default=fh 3:0 reserved. 3.6.15. iolimit2?i/o limit address register (device 2) address offset: 1dh default value: 00h access: read/write size: 8 bits this register controls the host to hub interface b i/o access routing based on the following formula: io_base2 address io_limit2 only the upper 4 bits are programmable. for the purpose of address decode, address bits a[11:0] are assumed to be fffh. thus, the top of the defined i/o address range will be at the top of a 4 kb aligned address block. bit description 7:4 i/o address limit: corresponds to a[15:12] of the i/o address limit of device 2. default=0 3:0 reserved. (only 16 bit addressing supported.)
102 datasheet 3.6.16. ssts2?secondary pci-pci status register (device 2) address offset: 1e?1fh default value: 02a0h access: read only, read/write clear size: 16 bits ssts2 reports the occurrence of error conditions associated with secondary side (i.e., hub interface b side ) of the ?virtual? pci-pci bridge embedded within mch. bit descriptions 15 detected parity error (dpe2)?r/wc: this bit is set to a 1 to indicate mch?s detection of a parity error in the address or data phase of hub interface b bus transactions. software clear this bit by writing a 1 to this bit. note that the function of this bit is not affected by the perre2 bit. also note that perr# is not implemented in the mch. 14 received system error (sse2)?r/wc: 1 = mch received an serr message across the hub interface b. 0 = software clears this bit by writing a 1 to this bit. 13 received master abort status (rmas2)?r/wc: 1 = mch terminates a host-to-hub interface b with an unexpected master abort. 0 = software clears this bit to 0 by writing a 1 to it. 12 received target abort status (rtas2)?r/wc: 1 = mch-initiated transaction on hub interface b is terminated with a target abort. 0 = software clear this bit by writing a 1 to it. 11 signaled target abort status (stas2)?ro: (not applicable). hardwired to 0. 10:9 devsel# timing (devt2)?ro: this 2-bit field indicates the timing of the devsel# signal when the mch responds as a target on hub interface b, and is hard-wired to the value 01b (medium) to indicate the time when a valid devsel# can be sampled by the initiator of the pci cycle. 01 = medium 8 data parity detected (dpd2)?ro: (not applicable). hardwired to 0. 7 fast back-to-back (fb2b2)?ro: mch as a target supports fast back-to-back transactions on hub interface b. hardwired to 1. 6 reserved 5 33/66mhz capable (cap66)?ro: hub interface b is capable of 66 mhz operation. hardwired to 1. 4:0 reserved.
82840 mch r datasheet 103 3.6.17. mbase2?memory base address register (device 2) address offset: 20?21h default value: fff0h access: read/write size: 16 bits this register controls the host to hub interface b non-prefetchable memory access routing based on the following formula: memory_base2 address memory_limit2 the upper 12 bits of the register are read/write and correspond to the upper 12 address bits a[31:20] of the 32 bit address. the lower 4 bits of this register are read-only and return zeroes when read. this register must be initialized by the configuration software. for the purpose of address decode, address bits a[19:0] are assumed to be 0. thus, the bottom of the defined memory address range will be aligned to a 1 mb boundary. bit description 15: 4 memory address base 2 (mem_base2): corresponds to a[31:20] of the lower limit memory address that will be passed by the device 2 to hub interface b. 3:0 reserved. 3.6.18. mlimit2?memory limit address register (device 2) address offset: 22?23h default value: 0000h access: read/write size: 16 bits this register controls the host to hub interface b non-prefetchable memory access routing based on the following formula: memory_base2 address memory_limit2 the upper 12 bits of the register are read/write and correspond to the upper 12 address bits a[31:20] of the 32 bit address. the lower 4 bits of this register are read-only and return zeroes when read. this register must be initialized by the configuration software. for the purpose of address decode, address bits a[19:0] are assumed to be fffffh. thus, the top of the defined memory address range will be at the top of a 1mb aligned memory block. bit description 15: 4 memory address limit 2(mem_limit2): bits 15:4 correspond to a[31:20] of the upper limit memory address that will be passed by the device 2 to hub interface b. default=0 3:0 reserved. note: memory range covered by mbase2 and mlimit2 registers are used to map non-prefetchable hub interface b address ranges (typically, where control/status memory-mapped i/o data structures of the graphics controller will reside) and pmbase2 and pmlimit2 are used to map prefetchable address ranges (typically, graphics local memory). this segregation allows application of uswc space attribute to be performed in a true plug-and-play manner to the prefetchable address range for improved host-hub interface b memory access performance.
104 datasheet 3.6.19. pmbase2?prefetchable memory base address register (device 2) address offset: 24?25h default value: fff0h access: read/write size: 16 bits this register controls the host to hub interface b prefetchable memory accesses routing based on the following formula: prefetchable_memory_base2 address prefetchable_memory_limit2 the upper 12 bits of the register are read/write and correspond to the upper 12 address bits a[31:20] of the 32 bit address. the lower 4 bits of this register are read-only and return zeroes when read. this register must be initialized by the configuration software. for the purpose of address decode, address bits a[19:0] are assumed to be 0. thus, the bottom of the defined memory address range will be aligned to a 1 mb boundary. bit description 15: 4 prefetchable memory address base 2(pmem_base2): bits 15:4 correspond to a[31:20] of the memory address. 3:0 reserved. 3.6.20. pmlimit2?prefetchable memory limit address register (device 2) address offset: 26?27h default value: 0000h access: read/write size: 16 bits this register controls the host to hub interface b prefetchable memory accesses routing based on the following formula: prefetchable_memory_base2 address prefetchable_memory_limit2 the upper 12 bits of the register are read/write and correspond to the upper 12 address bits a[31:20] of the 32 bit address. the lower 4 bits of this register are read-only and return zeroes when read. this register must be initialized by the configuration software. for the purpose of address decode, address bits a[19:0] are assumed to be fffffh. thus, the top of the defined memory address range will be at the top of a 1 mb aligned memory block. bit description 15: 4 prefetchable memory address limit 2(pmem_limit2): bits 15:4 correspond to a[31:20] of the memory address. default=0 3:0 reserved. note that prefetchable memory range is supported to allow segregation by the configuration software between the memory ranges that must be defined as uc and the ones that can be designated as a uswc (i.e. prefetchable) from the processor perspective .
82840 mch r datasheet 105 3.6.21. bctrl2?pci-pci bridge control register (device 2) address offset: 3eh default: 00h access: read/write size 8 bits this register provides extensions to the pcicmd2 register that are specific to pci-pci bridges. the bctrl2 provides additional control for the secondary interface (i.e., hub interface b) as well as some bits that affect the overall behavior of the ?virtual? pci-pci bridge in the mch (e.g., vga compatible address ranges mapping). bit descriptions 7 fast back to back enable?ro: the mch does not generate fast back-to-back cycles as a master on hub interface b. this bit is hardwired to 0. 6 secondary bus reset?ro: mch does not support generation of reset via this bit on the hub interface b. this bit is hardwired to 0. 5 master abort mode?ro: hardwired to 0. as a master on hub interface b the mch will discard data on writes and return all 1s during reads when a master abort occurs. 4 reserved 3 vga2 enable (vgaen2)?r/w: controls the routing of host initiated transactions targeting vga compatible i/o and memory address ranges. 1 = enable. the mch will forward the following host accesses to the hub interface b: ? memory accesses in the range 0a0000h?0bffffh ? i/o addresses where a[9:0] are in the ranges 3b0h?3bbh and 3c0h?3dfh (inclusive of isa address aliases: a[15:10] are not decoded) when enabled, forwarding of these accesses issued by the processor is independent of the i/o address and memory address ranges defined by the previously defined base and limit registers. forwarding of these accesses is also independent of the settings of bit 2 (isa enable) of this register, if this bit is 1. 0 = disable (default). vga compatible memory and i/o range accesses are not forwarded to hub interface b; rather, they are subtractively mapped to primary pci unless they are mapped to hub interface b via i/o and memory range registers defined above (iobase2, iolimit2, mbase2, mlimit2, pmbase2, pmlimit2) refer to the system address map chapter for further information. 2 isa enable?r/w: this bit modifies the response by the mch to an i/o access issued by the processor that target isa i/o addresses. this applies only to i/o addresses that are enabled by the iobase and iolimit registers. 1 = enable. mch will not forward to hub interface b any i/o transactions addressing the last 768 bytes in each 1 kb block, even if the addresses are within the range defined by the iobase and iolimit registers. instead of going to hub interface b, these cycles are forwarded to hub interface a where they can be subtractively or positively claimed by the isa bridge. 0 = disable (default). all addresses defined by the iobase and iolimit for processor i/o transactions will be mapped to hub interface b. 1 serr# enable (serre1)?r/w: this bit enables or disables forwarding of serr messages from hub interface b to hub interface a, where they can be converted into interrupts that are eventually delivered to the processor. 1 = enable. 0 = disable.
106 datasheet bit descriptions 0 parity error response enable?r/w: this bit controls mch?s response to data phase parity errors on hub interface b. 1 = address and data parity errors on hub interface b are reported via serr# mechanism, if enabled by serre2 and serren. 0 = address and data parity errors on hub interface b are not reported via the mch serr# signal. other types of error conditions can still be signaled via serr# independent of this bit?s state. 3.6.22. errcmd2?error command register (device 2) address offset: 40h default value: 00h access: read/write size: 8 bits bit description 7:1 reserved 0 serr on receiving target abort (serta): 1 = mch generates an serr message over hub interface a upon receiving a target abort on hub interface b. 0 = mch does not assert an serr message upon receipt of a target abort on hub interface b. serr messaging for device 2 is globally enabled in the pcicmd2 register.
82840 mch r datasheet 107 4. system address map a system based on the 82840 chipset supports 4 gb of addressable memory space and 64 kb+3 of addressable i/o space. the i/o and memory spaces are divided by system configuration software into regions. the memory ranges are useful either as system memory or as specialized memory, while the i/o regions are used solely to control the operation of devices in the system. the pentium ? ii and pentium ? iii processor families support addressing of memory ranges larger than 4 gb. the 82840 mch claims any access that maps neither to an expansion bus nor to system memory (including accesses over 4 gb) by terminating the transaction without forwarding it to hub interface a, hub interface b, or agp. when the mch receives a write request whose address targets an invalid space, the data is ignored. for reads, the mch responds by returning all 0s on the requesting interface. 4.1. memory address ranges the system memory map is broken into three categories: ? extended memory range (1 mb to 4 gb) - the extended memory range (1 mb to 4 gb) contains a 32 bit memory space. this memory space is used for mapping pci, agp, apic, smram, and bios memory spaces. ? dos compatible area (below 1 mb) - the dos compatibility area is a dos legacy space. it is used for bios and legacy devices on the lpc interface. figure 3. system address map dos legacy address range pci memory address range top of low memory main memory address range 4 gb 1 mb hublink_b agp graphics aperture independently programmable non- overlapping windows mem_map_1
108 datasheet 4.1.1. dos compatibility area this area is divided into the following address regions: ? 0 ? 640 kb dos area ? 640 ? 768 kb video buffer area ? 768 ? 896 kb in 16 kb sections (total of 8 sections) - expansion area ? 896 -960 kb in 16 kb sections (total of 4 sections) - extended system bios area ? 960 kb - 1 mb memory (bios area) - system bios area there are sixteen memory segments in the compatibility area. thirteen of the memory ranges can be enabled or disabled independently for both read and write cycles. table 7. memory segments and their attributes memory segments attributes comments 000000h ? 09ffffh fixed (always mapped to main dram) 0 to 640 kb (dos region) 0a0000h ? 0bffffh mapped to the hub interface or agp (configurable as smm space) video buffer (physical dram configurable as smm space) 0c0000h ? 0c3fffh we re add-on bios 0c4000h ? 0c7fffh we re add-on bios 0c8000h ? 0cbfffh we re add-on bios 0cc000h ? 0cffffh we re add-on bios 0d0000h ? 0d3fffh we re add-on bios 0d4000h ? 0d7fffh we re add-on bios 0d8000h ? 0dbfffh we re add-on bios 0dc000h ? 0dffffh we re add-on bios 0e0000h ? 0e3fffh we re bios extension 0e4000h ? 0e7fffh we re bios extension 0e8000h ? 0ebfffh we re bios extension 0ec000h ? 0effffh we re bios extension 0f0000h ? 0fffffh we re bios area dos area (00000h?9ffffh) the dos area is 640 kb in size and is always mapped to the main memory controlled by the mch. video buffer area (a0000h?bffffh) the 128 kb graphics adapter memory region is normally mapped to a legacy video device on the primary pci bus (pci_a) behind the hub interface (typically, a vga controller). this region is also the default region for smm space.
82840 mch r datasheet 109 accesses to this range can be directed to agp by setting the vgaen bit in the bctrl1 (pci-pci bridge control) register in device 1. in addition, accesses to this range can be directed to the hub interface b by setting the vgaen bit in the bctrl2 (pci-pci bridge control) register in device 2. the control is applied for accesses initiated from any of the system interfaces (i.e., processor bus , hub interface a/pci, hub interface b, and agp). note that no agp ? hub interface accesses are supported. the smram control register controls how smm accesses to this space are treated. compatible smram address range (a0000h?bffffh) when compatible smm space is enabled, smm mode processor accesses to this range are routed to physical dram at this address. non-smm-mode processor accesses to this range are considered to be to the video buffer area as described above. originated cycles from agp or the hub interface to enabled smm space are not allowed and are considered to be to the video buffer area. monochrome adapter (mda) range (b0000h?b7fffh) legacy support requires the ability to have a second graphics controller (monochrome) in the system. since the monochrome adapter may be on the hub interface a bus, the mch must decode cycles in the mda range and forward them to hub interface a. this capability is controlled by the mdap bit in device 0 configuration space register at offset beh). in addition to the memory range b0000h?b7fffh, the mch decodes io cycles at 3b4h, 3b5h, 3b8h, 3b9h, 3bah, and 3bfh and forwards them to the hub interface a bus. isa expansion area (c0000h?dffffh) this 128 kb isa expansion region is divided into eight 16 kb segments. each segment can be assigned one of four read/write states: read-only, write-only, read/write, or disabled. typically, these blocks are mapped through the mch and are subtractively decoded to the isa space. memory that is disabled is not remapped. extended system bios area (e0000h?effffh) this 64 kb area is divided into four 16 kb segments. each segment can be assigned independent read and write attributes so it can be mapped either to main dram or to the hub interface. typically, this area is used for ram or rom. memory segments that are disabled are not remapped elsewhere. system bios area (f0000h?fffffh) this area is a single 64 kb segment. this segment can be assigned read and write attributes. it is by default (after reset) read/write disabled and cycles are forwarded to the hub interface. by manipulating the read/write attributes, the mch can ?shadow? bios into the main dram. when disabled, this segment is not remapped.
110 datasheet figure 4. detailed dos compatible area address map mem_map_dos-area upper, lower, expansion card bios and buffer area 1mb 640 kb 768 kb 0c0000h 0a0000h controlled by pam[6:0]. monchrome display adapter space standard pci/isa video memory (smm memory) 0b8000h 0b0000h 736 kb 704 kb controlled by vga enable and mda enable. = dram = optionally dram = optionally agp 4.1.2. extended memory area this memory area contains the main dram address range. it is divided into regions as shown in figure 5. figure 5. detailed extended memory range address map mem_map_extend-mem 1_0000_0000 (4gb) fef0_0000 fee0_0000 fed0_0000 top of low memory (tom) fec0_0000 fec8_0000 ff00_0000 100a_0000 100c_0000 00f0_0000 (15 mb) 0100_0000 (16 mb) 0010_0000 (1mb) tem - tseg local apic space hublink_b i/o apic space hublink_a i/o apic space high bios, optional extended smram extended smram (translated to < 1mb) extended smram space region allowed for agp/pci, aperture, and hublink_b windows dram region optional dram region hublink_a (always) isa hole hublink_a (always) dram region dram region optional dram region
82840 mch r datasheet 111 isa hole memory space (0_00f0_0000 to 0_00ff_ffff) this memory hole is opened through the fdhc register (device 0, offset 58h). when it is enabled, accesses to this region are forward to hub interface a. extended smram address range the hseg and tseg smm transaction address spaces reside in this extended memory area. hseg (0_ffea_0000 to 0_ffeb_ffff) smm-mode processor accesses to enabled hseg are remapped to 000a0000h?000bffffh. non-smm- mode processor accesses to enabled hseg are considered invalid and remapped to address 0h (byte enables are deasserted for the writes). the exception to this rule are non-smm-mode write back cycles that are remapped to smm space to maintain cache coherency. originated cycle from agp or the hub interface to enabled smm space are not allowed. physical dram behind the hseg transaction address is not remapped and is not accessible. tseg (tom to tom - tseg) tseg can be up to 1 mb in size and is at the top of memory. smm-mode processor accesses to enabled tseg access the physical dram at the same address. non-smm-mode processor accesses to enabled tseg are considered invalid. the exception to this rule are non-smm-mode write back cycles that are directed to the physical smm space to maintain cache coherency. originated cycle from agp or the hub interface to enabled smm space are not allowed. apic configuration space (fec0_0000h?fecf_ffffh, fee0_0000h?feef_ffffh) this range is reserved for apic configuration space which includes the default i/o apic configuration space. the default local apic configuration space is fee0_0000h to feef_0fffh. the 82840 mch only decodes the fec0_0000h to fecf_ffffh range and forwards them to hub interface a or hub interface b. host accesses to the local apic configuration space do not result in external bus activity since the local apic configuration space is internal to the host. however, a mtrr must be programmed to make the local apic range uncacheable (uc). the local apic base address in each host should be relocated to the fec0_0000h (4 gb-20 mb) to fecf_ffffh range so that one mtrr can be programmed to 64 kb for the local and i/o apics. a fixed address decode region has been allocated for i/o apic. the fec0_0000 to fec7_ffffh address range is forwarded to hub interface a. the fec8_0000 to fecf_ffffh address range is forwarded to hub interface b. if hub interface b is not enabled, the cycle is forwarded to hub interface a. the 82840 mch does not support i/o apic on agp. if an access is attempted to an ioapic region from an io agent, the hub interfaces will terminate reads with a master-abort completion status. writes will simply be ignored.
112 datasheet agp memory and prefetchable memory plug-and-play software configures the agp memory window to provide enough memory space. accesses whose addresses fall within this window are decoded and forwarded to agp for completion. note that these registers (mbase1, mlimit1, mbase1,pmlimit1) must be programmed with values that place the agp memory space window between the value in the tom register and 4 gb. in addition, neither region should overlap with any other fixed or relocatable area of memory. hub interface b memory and prefetchable memory plug-and-play software configures the hub interface b memory window in order to provide enough memory space for the devices behind this pci-to-pci bridge. accesses whose addresses fall within this window are decoded and forwarded to hub interface b for completion. note that these registers (mbase2, mlimit2, pmbase2, pmlimit2) must be programmed with values that place the hub interface b memory space window between the value in the tom register and 4 gb. in addition, neither region should overlap with any other fixed or relocatable area of memory. hub interface a subtractive decode all accesses that fall between the value programmed into the tom register and 4 gb are subtractively decoded and forwarded to hub interface a, if they do not decode to a space that corresponds to another device. 4.1.3. agp memory address ranges the mch can be programmed to direct memory accesses to the agp bus interface when addresses are within either of two ranges specified via registers in mch device 1 configuration space. the first range is controlled via the memory base register (mbase1) and memory limit register (mlimit1) registers. the second range is controlled via the prefetchable memory base (pmbase1) and prefetchable memory limit (pmlimit1) registers. the mch positively decodes memory accesses to agp memory address space as defined by the following equations: memory_base_address address memory_limit_address prefetchable_memory_base_address address prefetchable_memory_limit_address the effective size of the range is programmed by the plug-and-play configuration software and it depends on the size of memory claimed by the agp device. note that the mch device 1 memory range registers described above are used to allocate memory address space for any devices sitting on agp bus that require such a window.
82840 mch r datasheet 113 4.1.4. agp dram graphics aperture memory-mapped, graphics data structures can reside in a graphics aperture to main dram memory . this aperture is an address range defined by the apbase and apsize configuration registers of the mch device 0. the apbase register follows the standard base address register template as defined by the pci 2.1 specification . the size of the range claimed by the apbase is programmed via ?back-end? register apsize (programmed by the chip-set specific bios before plug-and-play session is performed). apsize allows bios to pre-configure the aperture size to be either 4 mb, 8 mb,16 mb, 32 mb, 64 mb, 128 mb or 256 mb. by programming apsize to specific size, the corresponding lower bits of apbase are forced to ?0? (behave as hardwired). the apsize default value forces an aperture size of 256 mb. the aperture address range is naturally aligned. accesses within the aperture range are forwarded to the main dram subsystem. the mch translates the originally issued addresses via a translation table maintained in main memory. the aperture range should be programmed as non-cacheable in the processor caches. note: plug-and-play software configuration model does not allow overlap of different address ranges. therefore, the agp graphics aperture and agp memory address range are independent address ranges that may be adjacent, but cannot overlap one another. 4.1.5. system management mode (smm) memory range the mch supports the use of main memory as system management ram (smram) enabling the use of system management mode. the mch supports two smram options: compatible smram (c_smram) and extended smram (e_smram). system management ram (smram) space provides a memory area that is available for the smi handlers and code and data storage. this memory resource is normally hidden from the system operating system so that the processor has immediate access to this memory space upon entry to smm. the mch provides three smram options: ? below 1 mb option that supports compatible smi handlers. ? above 1 mb option that allows new smi handlers to execute with write-back cacheable smram. ? optional larger write-back cacheable t_seg area from 128 kb to 1 mb in size above 1 mb that is reserved from the highest area in system dram memory. the above 1 mb solutions require changes to compatible smram handlers code to properly execute above 1 mb. note: masters from the hub interface and agp are not allowed to access the smm space.
114 datasheet 4.1.5.1. smm space definition smm space is defined by its addressed smm space and its dram smm space. the addressed smm space is defined as the range of bus addresses used by the processor to access smm space. dram smm space is defined as the range of physical dram memory locations containing the smm code. smm space can be accessed at one of three transaction address ranges: compatible, high and tseg. the compatible and tseg smm space is not remapped and therefore the addressed and dram smm space is the same address range. since the high smm space is remapped the addressed and dram smm space is a different address range. note that the high dram space is the same as the compatible transaction address space. therefore the table below describes three unique address ranges: ? compatible transaction address (adr c) ? high transaction address (adr h) ? tseg transaction address (adr t) these abbreviations are used later in the table describing smm space transaction handling. smm space enabled transaction address space (adr) dram space (dram) compatible (c) a0000h?bffffh a0000h?bffffh high (h) 0ffea0000h?0ffebffffh a0000h?bffffh tseg (t) (tom - tseg_sz) to tom (tom-tseg_sz) to tom note: high smm is different than in previous chipsets. in previous chipsets the high segment was the 384 kb region from a0000h?fffffh. however, c0000h?fffffh is removed in the mch. note: tseg smm is different than in previous chipsets. in previous chipsets the tseg address space was offset by 256 mb to allow for simpler decoding and the tseg was remapped to just under the tom. in the mch the tseg region is not offset by 256 mb and it is not remapped. 4.1.5.2. smm space restrictions if any of the following conditions are violated, the results of smm accesses are unpredictable and may cause the system to hang up: ? the compatible smm space must not be setup as cacheable. ? high or tseg smm transaction address space must not overlap address space assigned to system dram, the agp aperture range, or to any ?pci? devices (including hub interface and agp devices). this is a bios responsibility. ? both d_open and d_close must not be set to 1 at the same time. ? when tseg smm space is enabled, the tseg space must not be reported to the operating system as available dram. this is a bios responsibility. ? any address translated through the agp aperture gtlb must not target dram from 000a0000h?000fffffh.
82840 mch r datasheet 115 4.1.6. memory shadowing any block of memory that can be designated as read-only or write-only can be ?shadowed? into mch dram memory. typically, this is done to allow rom code to execute more rapidly out of main dram. rom is used as a read-only during the copy process while dram at the same time is designated write- only. after copying, the dram is designated read-only so that rom is shadowed. host bus transactions are routed accordingly. 4.1.7. i/o address space the 82840 mch does not support the existence of any other i/o devices besides itself on the processor bus. the mch generates either hub interface a/pci, hub interface b, or agp bus cycles for all processor i/o accesses. the mch contains two internal registers in the processor i/o space? configuration address register (conf_addr) and configuration data register (conf_data). these locations are used to implement configuration space access mechanism as described in the configuration register chapter. the processor allows 64k+3 bytes to be addressed within the i/o space. the mch propagates the processor i/o address without any translation on to the destination bus and therefore, provides addressability for 64k+3 byte locations. note that the upper 3 locations can be accessed only during i/o address wrap-around when processor bus a16# address signal is asserted. a16# is asserted on the processor bus when an i/o access is made to 4 bytes from address 0fffdh, 0fffeh, or 0ffffh. a16# is also asserted when an i/o access is made to 2 bytes from address 0ffffh. the i/o accesses (other than ones used for configuration space access) are forwarded normally to either the hub interface a/pci bus or to hub interface b unless they fall within the agp i/o address range as defined by the mechanisms explained below. the mch will not post i/o write cycles to ide. the mch never responds to i/o cycles initiated on agp or either hub interface. 4.1.7.1. agp i/o address mapping the mch can be programmed to direct non-memory (i/o) accesses to the agp bus interface or to the hub interface b when processor-initiated i/o cycle addresses are within the agp i/o address range or the hub interface b i/o address range. the agp i/o range and the hub interface b i/o range are controlled via the i/o base address (iobase) and i/o limit address (iolimit) registers in mch device 1 and device 2 configuration space, respectively. the mch positively decodes i/o accesses to agp and hub interface b i/o address spaces as defined by the following equations: agp i/o device 1 i/o_base_address cpu i/o cycle address device 1 i/o_limit_address hub interface b i/o device 2 i/o_base_address cpu i/o cycle address device 2 i/o_limit_address the effective sizes of the ranges are programmed by the plug-and-play configuration software and depend on the size of i/o space claimed by the agp and hub interface b devices.
116 datasheet 4.1.8. mch decode rules and cross-bridge address mapping the address map described above applies globally to accesses arriving on any of the four interfaces (i.e., host bus, the hub interface a, hub interface b or agp). 4.1.8.1. the hub interface a decode rules the mch accepts accesses from the hub interface a to the following address ranges: ? all memory read and write accesses to main dram (except smm space). ? all memory write accesses from the hub interface a to agp memory range defined by mbase1, mlimit1, pmbase1, and pmlimit1. ? all memory read/write accesses to the graphics aperture defined by apbase and apsize. ? memory writes to vga range on agp, if enabled. all memory reads from the hub interface a that are targeted > 4 gb memory range will be terminated with master abort completion, and all memory writes (>4 gb) from the hub interface a will be ignored. 4.1.8.2. the hub interface b decode rules the mch accepts accesses from hub interface b to the following address ranges: ? all memory read and write accesses to main dram (except smm space). ? all memory write accesses from the hub interface to agp memory range defined by mbase1, mlimit1, pmbase1, and pmlimit1. ? all memory read/write accesses to the graphics aperture defined by apbase and apsize. ? memory writes to vga range on agp, if enabled. memory accesses from the hub interface b that fall elsewhere within the memory range and i/o cycles will not be accepted. they are terminated with master abort completion.
82840 mch r datasheet 117 4.1.8.3. agp interface decode rules cycles initiated using agp frame# protocol the mch does not support any agp frame# access targeting hub interface a. the mch claims agp- initiated memory read/write transactions decoded to the main dram range or the graphics aperture range. all other memory read/write requests will be master-aborted by the agp initiator as a consequence of the mch not responding to a transaction. under certain conditions, the mch restricts access to the dos compatibility ranges governed by the pam registers by distinguishing access type and destination bus. the mch does not accept agp frame# write transactions to the compatibility ranges if the pam designates dram as writable. if accesses to a range are not write enabled by the pam, the mch does not respond and the cycle results in a master-abort. the mch accepts agp frame# read transactions to the compatibility ranges if the pam designates dram as readable. if accesses to a range are not read enabled by the pam, the mch does not respond and the cycle results in a master-abort. if an agent on agp issues an i/o, pci configuration, or pci special cycle transaction, the mch will not respond and cycle results in a master-abort. cycles initiated using agp pipe# or sb protocol all cycles must reference main memory, main dram address range (including pam), or graphics aperture range (also physically mapped within dram but using different address range). agp accesses to smm space are not allowed. agp-initiated cycles that target dram are not snooped on the host bus, even if they fall outside of the agp aperture range. if a cycle is outside of main memory range, the cycle terminates as follows: ? reads: remap to memory address 0h, return data from address 0h, and set the iaaf error bit in errsts register in device 0 ? writes: terminated internally without affecting any buffers or main memory agp accesses to mch that cross device boundaries for agp frame# accesses, when an agp master gets disconnected, it will resume at the new address; this allows the cycle to be routed to or claimed by the new target. therefore, accesses should be disconnected by the target on potential device boundaries. the mch disconnects agp frame# transactions on 4 kb boundaries. agp pipe# and sba accesses are limited to 256 bytes and must hit dram. read accesses crossing a device boundary returns invalid data when the access crosses out of dram. write accesses crossing out of dram are discarded. the iaaf error bit is set.
118 datasheet 4.1.8.4. legacy vga ranges the legacy vga memory range a0000h?bffffh is mapped either to hub interface a, hub interface b, or agp. this behavior is configured by the programming of the vga enable bits in the bctrl configuration registers in mch device 1 and device 2 configuration spaces, as well as the mdap bit in the mchconf configuration register in device 0 configuration space. the same registers control mapping of vga i/o address ranges. vga i/o range is defined as addresses where a[9:0] are in the ranges 3b0h?3bbh and 3c0h?3dfh (inclusive of isa address aliases: a[15:10] are not decoded). the function and interaction of these three bits is described below: vga enable: controls the routing of processor-initiated transactions targeting vga compatible i/o and memory address ranges. when one of these bits is set , the mch forwards the following processor accesses (vga references) to either agp or hub interface b: ? memory accesses in the range 0a0000h to 0bffffh ? i/o addresses where a[9:0] are in the ranges 3b0h?3bbh and 3c0h?3dfh (inclusive of isa address aliases - a[15:10] are not decoded) mda references are defined as the following: ? memory: 0b0000h?0b7fffh ? i/o: 3b4h, 3b5h, 3b8h, 3b9h, 3bah, 3bfh, (including isa address aliases, a[15:10] are not used in decode) mda-only references are defined as the following: ? i/o 3bfh and its aliases. the following table shows the behavior for all combinations of mda and vga: vgaen1 (device 1) vgaen2 (device 2) mdap behavior 0 0 0 all references to mda and vga go to hub interface a 0 0 1 illegal combination: do not use 0 1 0 all references to vga go to hub interface b. addresses 3b4h, 3b5h, 3b8h, 3b9h, 3bah and their ailases are both mda and vga references, and they go to hub interface b. mda-only references go to hub interface a. 0 1 1 vga references go to hub interface b. mda-only references go to hub interface a 1 0 0 all references to vga go to agp addresses 3b4h, 3b5h, 3b8h, 3b9h, 3bah and their ailases are both mda and vga references, and they go to agp. mda-only references go to hub interface b 1 0 1 vga references go to agp. mda-only references go to hub interface a 1 1 0 illegal combination: do not use 1 1 1 illegal combination: do not use
82840 mch r datasheet 119 5. functional description 5.1. host interface the 82840 mch is optimized to support the pentium ? ii processor or pentium ? iii processor with the bus clock frequencies of 133 mhz or 100 mhz. the mch supports up to two processors at fsb frequencies of 100/133 mhz using agtl+ signaling. note that one of the two processors? agent id needs to be assigned as ?id# 0? in the system. it supports either 32- or 36-bit host addresses, allowing the processor to access the entire 4 gb of the mch?s memory address space. the mch has an 8-deep in-order queue to support up to eight outstanding pipelined address requests on the host bus. host- initiated i/o cycles are positively decoded to agp/pci, hub interface b, or mch configuration space and subtractively decoded to hub interface a. host initiated memory cycles are positively decoded to agp/pci, hub interface b, or dram and are again subtractively decoded to hub interface a. agp semantic memory accesses initiated from agp to dram are not snooped on the host bus. memory accesses initiated from agp using pci semantics and from either hub interfaces to dram will be snooped on the host bus. memory accesses whose addresses lie within the agp aperture are translated using the agp address translation table, regardless of the originating interface. the mch recognizes and supports a large subset of the transaction types that are defined for the pentium ? ii processor bus interface. however, each of these transaction types has a multitude of response types, some of which are not supported by the mch. all transactions are processed in the order that they are received on the host bus. a summary of transactions supported by the mch is given in the following table. table 8. p6 bus transactions supported by the mch transaction reqa[4:0]# reqb[4:0]# mch support deferred reply 0 0 0 0 0 x x x x x the mch initiates a deferred reply for a previously deferred transaction. reserved 0 0 0 0 1 x x x x x reserved interrupt acknowledge 0 1 0 0 0 0 0 0 0 0 interrupt acknowledge cycles are forwarded to the hub interface a or hub interface b a single byte of data is returned on hd[7:0]#. special transactions 0 1 0 0 0 0 0 0 0 1 see separate table in special cycles section. reserved 0 1 0 0 0 0 0 0 1 x reserved reserved 0 1 0 0 0 0 0 1 x x reserved branch trace message 0 1 0 0 1 0 0 0 0 0 the mch terminates a branch trace message without latching data. reserved 0 1 0 0 1 0 0 0 0 1 reserved reserved 0 1 0 0 1 0 0 0 1 x reserved reserved 0 1 0 0 1 0 0 1 x x reserved
120 datasheet transaction reqa[4:0]# reqb[4:0]# mch support i/o read 1 0 0 0 0 0 0 x len# i/o read cycles are forwarded to the hub interface a, hub interface b, or agp. i/o cycles to the mch configuration space will not be forwarded to agp or the hub interfaces. i/o write 1 0 0 0 1 0 0 x len# i/o write cycles are forwarded to the hub interface a, hub interface b or agp. i/o cycles to the mch configuration space are not forwarded to agp or the hub interface. reserved 1 1 0 0 x 0 0 x x x reserved memory read and invalidate 0 0 0 1 0 0 0 x len# host-initiated memory read and invalidate cycles are forwarded to dram. the mch initiates an mri (len=0) cycle to snoop a hub interface a, hub interface b or agp initiated write cycle to dram. reserved 0 0 0 1 1 0 0 x len# reserved memory code read 0 0 1 0 0 0 0 x len# memory code read cycles are forwarded to dram, hub interface a, hub interface b or agp. memory data read 0 0 1 1 0 0 0 x len# host-initiated memory read cycles are forwarded to dram, the hub interface a, hub interface b or agp. the mch initiates a memory read cycle to snoop a hub interface a, hub interface b or agp initiated read cycle to dram. memory write (no retry) 0 0 1 0 1 0 0 x len# this memory write is a writeback cycle and cannot be retried. the mch forwards the write to dram. memory write (can be retried) 0 0 1 1 1 0 0 x len# the standard memory write cycle is forwarded to dram, hub interface a, hub interface b , or agp. notes: 1. for memory cycles, reqa[4:3]# = asz#. 2. reqb[4:3]# = dsz#. for the pentium? pro processor, dsz# = 00 (64 bit data bus size). 3. len# = data transfer length as follows: len# data length 00 <= 8 bytes (be[7:0]# specify granularity) 01 length = 16 bytes be[7:0]# all active 10 length = 32 bytes be[7:0]# all active 11 reserved
82840 mch r datasheet 121 table 9. types of responses supported by the mch rs2# rs1# rs0# description mch support 0 0 0 idle 0 0 1 retry response this response is generated if an access is to a resource that cannot be accessed by the processor at this time and the logic must avoid deadlock. ich directed reads and writes, dram locked reads, agp reads and writes can be retried. 0 1 0 deferred response this response can be returned for all transactions that can be executed ?out of order.? host memory reads i/o reads, interrupt acknowledge and i/o writes cycles to the hub interface a, hub interface b and agp can be deferred. 0 1 1 reserved reserved 1 0 0 hard failure not supported. 1 0 1 no data response this is for transactions where the data has already been transferred or for transactions where no data is transferred. writes and zero length reads receive this response. 1 1 0 implicit writeback this response is given for those transactions where the initial transactions snoop hits on a modified cache line. 1 1 1 normal data response this response is for transactions where data accompanies the response phase. reads receive this response. host addresses above 4 gb host memory writes to address space above 4 gb are discarded without affecting the system state. host memory reads to address space above 4 gb are immediately terminated and return with a fixed value. host bus cycles the following transaction descriptions illustrate the various operations in their most straightforward representation. partial reads partial read transactions include i/o reads and memory read operations of less than or equal to eight bytes ( four consecutive bytes for i/o) within an aligned 8 byte span. the byte enable signals, be[7:0]#, select which bytes in the span to read. part-line read and write transactions the mch does not support partial-line (i.e., 16-byte) transactions. cache line reads a read of a full cache line (as indicated by the len[1:0]=10 during request phase) requires 32 bytes of data to be transferred. this translates into four data transfer cycles for a given request. since the mch is the only response agent in the system, it is always selected as the target and will determine whether the address is directed to dram, the hub interface a, the hub interface b, or agp and provide the corresponding command and control to complete the transaction.
122 datasheet partial writes partial write transactions include: i/o and memory write operations of eight bytes or less (maximum of four bytes for i/o) within an aligned 8 byte span. the byte enable signals, be[7:0]#, select which bytes in the span to write. i/o writes crossing a 4 byte boundary are broken into two separate transactions by the processor. cache line writes a write of a full cache line requires 32 bytes of data to be transferred; this translates into four data transfer cycles for a given request. memory-read-and-invalidate (length > 0) a memory-read-and-invalidate (mri) transaction is functionally equivalent to a cache line read. the purpose of having this special transaction is to support write allocation (write miss case) of cache lines in the processors. when a processor issues an mri, the cache line is read as in a normal cache line read operation; however, all other caching agents must invalidate this line if they have it in a shared or exclusive state. if a caching agent has this line in the modified state, it must be written back to memory and invalidated and it is . the mch captures the write-back data. it is illegal for a bus agent to assert hit# on this transaction. memory-read-and-invalidate (length = 0) a memory read and invalidate transaction of length zero (mri0) does not have an associated data response. executing the transaction informs other agents in the system that the agent issuing this request requires exclusive ownership of a cache line that maybe in the shared state (write hit to a shared line). agents with this cache line invalidate the line. if this line is in the modified state, an implicit write-back cycle is generated and the mch captures the data. memory read (length = 0) a memory read of length zero, mr(0) does not have an associated data response. this transaction is used by the mch to snoop for the hub interface to dram and agp frame# snoopable dram read accesses. the mch snoop request policy is identical for the hub interface and agp frame# memory read transactions. note that the mch will do multiple snoop ahead cycles for a hub interface burst reads greater than 32 bytes and for agp frame# master burst read (i.e., memory read multiple) to dram. the mch performs single mr(0) cycles for the hub interface reads less than or equal to 32 bytes and for agp frame# master standard read or read line directed to dram. the mch generates length=0 memory read cycles for the hub interface and agp frame# memory read cycles to dram. cache coherency cycles the mch generates an implicit writeback response during host bus read and write transactions when a processor asserts hitm# during the snoop phase. the host-initiated write case can have two data transfers, the requesting agents data followed by the snooping agents writeback data. the mch performs a memory read and invalidate cycle of length 0 (mri[0]) on the host bus when a hub interface or agp frame# snoopable dram read or write cycle occurs.
82840 mch r datasheet 123 interrupt acknowledge cycles a processor agent issues an interrupt acknowledge cycle in response to an interrupt from an 8259- compatible interrupt controller. the interrupt acknowledge cycle is similar to a partial read transaction, except that the address bus does not contain a valid address. interrupt acknowledge cycles are always directed to the hub interface a (never to agp). locked cycles the mch supports resource locking due to the assertion of the lock# line on the host bus as follows: ? host<->dram locked cycles. the mch supports host to dram locked cycles. the p6 bus protocol ensures that the host bus will execute any other transactions until the locked cycle is complete. the mch arbiter may grant another hub interface a, hub interface b, or agp device; however, any cycles to dram requiring cache coherency will be blocked. ? host<-> ich locked cycles. any host to the ich locked transaction will initiate a locked sequence to the hub interface a. the p6 bus implements a bus lock mechanism that ensures that no change of bus ownership can occur from the time one agent has established a locked transaction (i.e., the initial read cycle of a locked transaction has completed) until the locked transaction is completed. note that for host transactions to hub interface a, a ?lock? special cycle is issued to establish the lock prior to the initial read and a ?unlock? special cycle is issued to the hub interface a after the host lock transaction is completed. any concurrent cycle that requires snooping on the host bus is not processed while a lock transaction is occurring on the host bus. locked cycles from hub interface a to dram are not supported. ? host<->agp locked cycles. any host-agp lock cycle result in a un-predictable system behavior. ? host<->p64h locked cycles. the mch does not support a master abort on the second read of a split lock from the host. branch trace cycles an agent issues a branch trace cycle for taken branches if execution tracing is enabled. address aa[35:3]# is reserved and can be driven to any value. d[63:32]# carries the linear address of the instruction causing the branch and d[31:0]# carries the target linear address. the mch responds and retires this transaction but does not latch the value on the data lines or provide any additional support for this type of cycle. special cycles a special cycle is defined when reqa[4:0] = 01000 and reqb[4:0]= xx001. in the first address phase aa[35:3]# is undefined and can be driven to any value. in the second address phase, ab[15:8]# defines the type of special cycle issued by the processor. all host initiated special cycles are routed to the hub interface a. a special cycle is ?posted? into the mch and the fsb transaction is terminated immediately after the cycle has been broadcast. it does not wait for the cycle to propagate or terminate on the hub interface interface.
124 datasheet table 10 specifies the cycle type and definition as well as the action taken by the mch when a special cycle is identified. note that none of the host bus special cycles are propagated to either the agp interface or the hub interface b. table 10. types of special cycles supported by the mch be[7:0]# special cycle type action taken 0000 0000 nop this transaction has no side-effects. 0000 0001 shutdown this transaction is issued when an agent detects a severe software error that prevents further processing. this cycle is claimed by the mch and propogated as a shutdown special cycle over the hub interface a. this cycle is retired on the host bus after the associated special cycle request is successfully broadcast over the hub interface. 0000 0010 flush this transaction is issued when an agent has invalidated its internal caches without writing back any modified lines. the mch claims this cycle and simply retires it. 0000 0011 halt this transaction is issued when an agent executes a hlt instruction and stops program execution. this cycle is claimed by the mch and propagated over the hub interface a as a halt special cycle. this cycle is retired on the host bus after the associated special cycle request is successfully broadcast over the hub interface. 0000 0100 sync this transaction is issued when an agent has written back all modified lines and has invalidated its internal caches. the mch claims this cycle and simply retires it. 0000 0101 flush acknowledge this transaction is issued when an agent has completed a cache sync and flush operation in response to an earlier flush# signal assertion. the mch claims this cycle and retires it. 0000 0110 stop grant acknowledge this transaction is issued when an agent enters stop grant mode. this cycle is claimed by the mch and propagated over the hub interface a as a stop grant special cycle. this cycle is retired on the host bus after the associated special cycle request is successfully broadcast over the hub interface. 0000 0111 smi acknowledge this transaction is first issued when an agent enters the system management mode (smm). ab[7]# is also set at this entry point. all subsequent transactions from the host with ab[7]# set are treated by the mch as accesses to the smm space. no corresponding cycle is propagated to the hub interface. to exit the system management mode the host issues another one of these cycles with the ab[7]# bit deasserted. the smm space access is closed by the mch at this point. all others reserved
82840 mch r datasheet 125 5.1.1. frame buffer memory support to allow for high speed write capability for graphics, the pentium ii processor introduced wc (write- combined memory type). uswc is uncacheable, speculative, write-combining. the uswc memory type provides a write-combining buffering mechanism for write operations. a high percentage of graphics transactions are writes to the memory-mapped graphics region, normally known as the linear frame buffer. reads and writes to uswc are non-cached and are not allowed to have side effects. in the case of graphics, current 32-bit drivers (without modifications) would use a partial write protocol to update the frame buffer. the highest performance write transaction on the host bus is the line write. by combining several back-to-back partial write transactions (internal to the processor) into a line write transaction on the processor bus, the performance of frame buffer accesses would be greatly improved. writes to uswc memory can be buffered and combined in the processor's write-combining buffers (wcb). the wcb is flushed after executing a serializing, locked, i/o instruction, or the wcb is full (32 bytes). to extend this capability to the current drivers, it is necessary to set up the linear frame buffer address range to be uswc memory type. this can be done by programming the mtrr registers in the processor. note that the application of uswc memory attribute is not limited only to the frame buffer support and that the mch implements write combining for any host to the hub interface or host to agp posted write. 5.2. agp interface the mch support 3.3v agp 1x/2x, and 1.5v agp 1x/2x/4x devices. to support these modes of operation, the agp signal buffers are designed with two modes of operation: ? 3.3v drive/receive (not 5 volt tolerant) ? 1.5v drive/receive (not 3.3 volt tolerant). the mch supports 2x/4x clocking transfers for read and write data, and for sideband addressing. it will also support 2x and 4x clocking for fast writes initiated from the mch (on behalf of the processor). agp pipe# or sba[7:0] transactions to dram are not snooped and are, therefore, not coherent with the processor caches. agp frame# transactions to dram are snooped. agp pipe# and sba[7:0] accesses to and from the hub interface a or hub interface b are not supported. agp frame# access from an agp master to the hub interface are also not supported. only the agp frame memory writes from the hub interface are supported. 5.2.1. agp target operations as an initiator, the mch does not initiate cycles using agp enhanced protocols. the mch supports agp cycles targeting interface to main memory only. the mch supports interleaved agp pipe# and agp frame#, or agp sba[7:0] and agp frame# transactions.
126 datasheet table 11. agp commands supported by the mch when acting as an agp target mch host bridge agp command c/be[3:0]# encoding cycle destination response as pcix target read 0000 main memory low priority read 0000 the hub interface complete with random data hi-priority read 0001 main memory high priority read 0000 the hub interface complete with random data reserved 0010 n/a no response reserved 0011 n/a no response write 0100 main memory low priority write 0100 the hub interface cycle goes to dram with bes inactive hi-priority write 0101 main memory high priority write 0101 the hub interface cycle goes to dram with bes inactive - does not go to the hub interface reserved 0110 n/a no response reserved 0111 n/a no response long read 1000 main memory low priority read the hub interface complete locally with random data - does not go to the hub interface hi-priority long read 1001 main memory high priority read the hub interface complete with random data flush 1010 mch complete with qw of random data reserved 1011 n/a no response fence 1100 mch no response - flag inserted in mch request queue reserved 1101 n/a no response reserved 1110 n/a no response reserved 1111 n/a no response notes: n/a refers to a function that is not applicable as a target of an agp cycle, the mch supports all the transactions that directly forward main memory and these are summarized in the table above. the mch supports both normal and high priority read and write requests. the mch does not support agp cycles to either hub interfaces. pipe# and sba cycles do not require coherency management and all agp initiator accesses to main memory using agp pipe# or sba protocol are treated as non-snoopable cycles. these accesses are directed either to the agp aperture in main memory or to the un-translated main memory outside of the graphics aperture the memory space covered by the aperture should be programmed as either uncacheable (uc) memory or write combining (wc) in the intel ? pentium ? pro processor?s mtrrs.
82840 mch r datasheet 127 5.2.2. agp transaction ordering the mch observes transaction ordering rules as defined by the agp interface specification, revision 2.0 . 5.2.3. agp electricals the 4x data transfers use 1.5v signaling levels as described in the agp 2.0 specification . the mch supports 1x/2x data transfers using either the 3.3v or 1.5v signaling levels. the mechanism to select the data transfer mode is orthogonal to the mechanism to select the signaling level. the following table shows the data rates and signaling levels supported by the mch. signaling level data rate 1.5v 3.3v 1x agp* yes yes 2x agp yes yes 4x agp yes no * note that agp frame# data rate and signaling level is the same as 1x agp. 5.2.4. the differences between agp frame# and pci-66 devices ? mch supports only one agp frame# device. ? the agp frame# device must meet the agp 2.0 electrical specification. ? lock# signal is not present for agp frame#. neither inbound or outbound locks are supported. ? serr# signal is present for agp frame#. ? perr# signal is not present for agp frame#. ? 16 clock subsequent data latency timer (instead of 8) for agp frame# devices. note pci-66 devices are not supported on the agp interface unless they comply with the agp 2.0 specification. 5.2.5. 4x agp protocol in addition to the 1x and 2x agp protocol, the mch supports 4x agp read and write data transfers, and 4x sideband address generation. the 4x operation is compliant with agp 2.0 specification. the mch indicates that it supports 4x data transfers thro ugh rate[2] (bit 2) of the agp status register. when data_rate[2] (bit 2) of the agp command register is 1 during system initialization, the mch performs agp read and write data transactions using 4x protocol. this bit is not dynamic. once this bit is set during initialization, the data transfer rate may not change. the 4x data rate transfer provides 1.06 gb/s transfer rates. the control signal protocol for the 4x data transfer protocol is identical to 1x/2x protocol. in 4x mode 16 bytes of data are transferred on every 66 mhz clock edge. the minimum throttleable block size remains four 66 mhz clocks which means 64 bytes of data is transferred per block. three additional signal pins are required to implement the 4x data transfer protocol. these signal pins are complimentary data transfer strobes for the ad bus (2) and the sba bus (1).
128 datasheet 5.2.6. fast writes the mch supports 2x and 4x fast writes from the mch to the graphics controller on agp. fast write operation is compliant with fast writes as currently described in agp 2.0. the mch indicates that it supports fast writes thro ugh bit 4 (fw) of the agp status register. when fw_enable (bit 4 ) of the agp command register is 1, the mch uses fast write protocol to transfer memory write data to the agp master. memory writes originating from the host(s) or from the hub interface use the fast write protocol, when it is enabled. the data rate used to perform the fast writes is dependent on which bit is set in data_rate[2:0] (bits 2:0) of the agp command register. if data_rate[2]=1, the data transfers occur using 4x strobing. if data_rate[1]=1, the data transfers occur using 2x strobing. if data_rate[0] =1, fast writes are disabled and occur using standard pci protocol. note that only one of the three data_rate bits may be set by initialization software. this is summarized in the following table. table 12. fast write register programming fw_enable data_rate[2] data_rate[1] data_rate[0] mch =>agp master write protocol 0 x x x 1x 1 0 0 1 1x 1 0 1 0 2x strobing 1 1 0 0 4x strobing 5.2.7. agp universal connector the mch supports the agp universal connector that allows either a 1.5v or a 3.3v agp add-in card to be supported by the system. 5.2.8. agp frame# transactions on agp the mch accepts and generates agp frame# transactions on the agp bus. the mch guarantees that agp frame# accesses to dram are kept coherent with the processor caches by generating snoops to the host bus. lock#, serr#, and perr# signals are not supported.
82840 mch r datasheet 129 5.2.8.1. mch initiator and target operations table 13 summarizes mch target operation for agp frame# initiators. these cycles target only to main memory. table 13. pci commands supported by the mch when acting as a frame# target mch pci command c/be[3:0]# encoding cycle destination response as a frame# target interrupt acknowledge 0000 n/a no response special cycle 0001 n/a no response i/o read 0010 n/a no response i/o write 0011 n/a no response reserved 0100 n/a no response reserved 0101 n/a no response memory read 0110 main memory read 0110 the hub interface no response memory write 0111 main memory posts data 0111 the hub interface no response reserved 1000 n/a no response reserved 1001 n/a no response configuration read 1010 n/a no response configuration write 1011 n/a no response memory read multiple 1100 main memory read 1100 the hub interface a/b no response dual address cycle 1101 n/a no response memory read line 1110 main memory read 1110 the hub interface a/b no response memory write and invalidate 1111 main memory posts data 1111 the hub interface a/b posts data notes: n/a refers to a function that is not applicable
130 datasheet mch as target of agp frame# cycle (supported transactions) ? memory read, memory read line, and memory read multiple. these commands are supported identically by the mch. the mch does not support reads of the hub interface bus from agp. ? memory write and memory write and invalidate. these commands are aliased and processed identically. ? other commands. other commands such as i/o r/w and configuration r/w are not supported by mch as a target and result in master abort. ? exclusive access. the mch does not support pci locked cycles as a target. ? fast back-to-back transactions. the mch, as a target, supports fast back-to-back cycles from an agp frame# initiator. mch as initiator of agp frame# cycle (supported transactions) ? memory read and memory read line. the mch supports reads from host to agp. the mch does not support reads from either hub interfaces to agp. ? memory read multiple. this command is not supported by the mch as an agp frame# initiator. ? memory write. the mch initiates agp frame# cycles on behalf of the host or the hub interface. the mch does not issue memory write and invalidate as an initiator. mch does not support write merging or write collapsing. the mch allows non-snoopable write transactions from the hub interface to the agp bus. ? i/o read and write. i/o read and write from the host are sent to the agp bus. i/o base and limit address range for agp bus are programmed in agp frame# configuration registers. all other accesses that do not correspond to this programmed address range are forwarded to the hub interface a. ? exclusive access. the mch will not issue a locked cycle on the agp bus on behalf of either the host or the hub interface. the hub interface and host locked transactions to agp are initiated as unlocked transactions by the mch on the agp bus. ? configuration read and write. host configuration cycles to agp are forwarded as type 1 configuration cycles. ? fast back-to-back transactions. the mch, as an initiator, does not perform fast back-to-back cycles.
82840 mch r datasheet 131 5.2.8.2. mch retry/disconnect conditions the mch generates retry/disconnect according to the agp specification rules when being accessed as a target from the agp frame# device. 5.2.8.3. delayed transaction when a agp frame#-to-dram read cycle is retried by the mch, the cycle is processed internally as a delayed transaction. the mch supports the delayed transaction mechanism on the agp target interface for the transactions issued using agp frame# protocol. this mechanism is compatible with the pci 2.1 specification. the process of latching all information required to complete the transaction, terminating with retry, and completing the request without holding the master in wait-states is called a delayed transaction. the mch latches the address and command when establishing a delayed transaction. the mch generates a delayed transaction on agp only for agp frame# to dram read accesses. the mch does not allow more than one delayed transaction access from agp at any time.
132 datasheet 5.3. rdram interface the 82840 mch directly supports dual channels(interfaces) of rambus* direct memory operating in lock-step using rsl technology. the mch support two different operation modes: ? single channel-pair mode. the mch is configured to directly support rdram devices on its dual rambus* interfaces. there is no mrh-r used on the memory subsystem. a maximum of 64 rdram devices are supported on the paired channels without external logic. ? multiple channel-pair mode. the mch is configured to use mrh-r on the memory subsystem. each rambus* channel of the mrh-r on the mch direct rambus* interface a is paired with one rambus* channel of the mrh-r on the direct rambus* interface b. the mch supports one mrh-r per interface and each mrh-r can support up to 2 rdram channels. therefore, up to 4 rdram channels are supported by the mch with a total of 2 mrh-rs (1 mrh-r per interface). the interface between the mch and direct rdram devices is referred to either as a ?channel" or as an ?expansion channel.? the channel interface consists of 33 signals including clocks (30 are rsl signals and 3 are cmos signals). when mrh-r is used for channel expansion, there are two additional rsl signals per channel. figure 6 shows the interconnections between mch and its dual direct rdram channels configured in single channel-pair mode. figure 6. single channel-pair mode 82840 mch channel a rdram cfm, cfm# rq[7:0] dq[15:0], dqp[1:0] sfm, stm, scfm ctm, ctm# terminator cfm, cfm# rq[7:0] dq[15:0], dqp[1:0] sfm, stm, scfm gen clock channel b rdram cfm, cfm# rq[7:0] dq[15:0], dqp[1:0] sfm, stm, scfm ctm, ctm# terminator cfm, cfm# rq[7:0] dq[15:0], dqp[1:0] sfm, stm, scfm gen clock single_pr-ch
82840 mch r datasheet 133 figure 7 shows the interconnections between mch and its dual direct rdram channels configured at multiple channel-pair mode. figure 7. multiple channel-pair mode multi_pr-ch terminator rambus expansion channel b mrh-r 82840 mch up to 32 rdram devices terminator rambus expansion channel a mrh-r the maximum system memory supported by mch depends on the direct rdram device technology (table 14). table 14. maximum memory supported for various configurations directly supported supported via mrh-r(s) rdram increments maximum increments maximum 64mb 16 mb 512 mb 16 mb 1 gb 128mb 32 mb 1 gb 32 mb 2 gb 256mb 6 4mb 2 gb 64 mb 4 gb the row, column, and bank address bits required for the direct rdram device depends on the number of banks and page size of device. table 15 shows the different combinations supported by the mch.
134 datasheet table 15. direct rdram device configurations cf# device tech device capacity in mb # of banks (d= dependent) page size # of bank address bits # of row address bits # of column address bits 1 64mbit 8 16 (d) 1 kb 4 9 6 2 128mbit 16 2x16 (d) 1 kb 5 9 6 3 32 2x16 (d) 1 kb 5 10 6 4 256mbit 32 2x16 (d) 2 kb 4 10 7 a brief overview of the registers that configure the direct rdram interface is provided below: ? group boundary address register (gba). gba registers define the upper and lower addresses for a group of direct rdram device pairs in a channel-pair. each group requires a separate gba register. each group consists of 4 device-pairs in single channel mode and 8 device-pairs in multiple channel mode. the mch contains 16 gba registers. ? group architecture register (gar). gar registers specify the architecture features of each group of device pairs in a channel pair. the architecture features specified are bank type and device core technology. each gar represents a group consisting of 4 device-pairs in single channel mode and 8 device-pairs in multiple channel mode. there is a 1:1 correspondence between gba and gar registers. ? rdram timing register (rdtr). the dtr defines the timing parameters for all devices in all channels. the bios programs this register with ?least common denominator? values after reading configuration registers of each device in the channels. ? rdram pool sizing register (rpmr). this register provides bits to program the number of rdram device-pair in one of three rdram power management states. ? rdram initialization control register (ricm). this register provides bits to program mch to do initialization activities on direct rdram devices. 5.3.1. rdram organization and configuration the mch supports 16/18-bit direct rdram configurations. the mch supports a maximum of 64 rdram devices (32 devices per channel) on its dual direct rdram channels. direct rdram channel can be populated with a mix of 64mbit, 128mbit, and 256mbit direct rdram devices.
82840 mch r datasheet 135 5.3.1.1. rules for populating rdram devices mch rambus* channels can be implemented such that it is fully or partially loaded with rdram devices; however, they must be populated in either single-device pair or multiple-device pair. ? single device-pair. the 82840 mch is configured to directly support rdram devices on its dual rambus* channel. each rdram device of the mch direct rambus* interface a is paired with one rdram device of the direct rambus* interface b. there is no mrh-r used on the memory subsystem. ? multiple device-pair. the 82840 mch is configured to use mrh-r on the memory subsystem. each rdram deivce on direct rambus* interface a is paired with one rdram device on the direct rambus* interface b. from the mch point-of-view, all device-pairs in the channels are grouped into logical groups. system initialization software partitions the rdrams into groups of four device-pairs in single channel mode operation and into groups of eight device-pairs in multiple channel mode operation. as a result, there can be a maximum of 8 groups per channel-pair in single channel-pair operation and a maximum of 4 groups per channel pair in multiple channel-pair mode. all device-pairs populated in a group must be of the same architecture. that is, all device-pairs in a group must be the same core technology, and have the same number of banks. following are the rules for populating the groups: ? a group can be partially populated. ? there is no requirement that group members have to be populated in contiguous physical slots. ? there can be a maximum of 8 groups in single channel-pair mode or 4 groups per channel in multiple channel-pair mode. a member that does not belong to any of the groups in the channel will not be recognized. the following table provides the device ids for members in all groups. table 16. rdram device grouping single channel mode multiple channel mode device-pair ids for group members group name device pair ids for group members group name 0, 1, 2, 3 group#0 0, 1, 2, 3, 4, 5, 6, 7, ch#0 pair, group#0 4, 5, 6, 7 group#1 8, 9, 10, 11, 12, 13, 14, 15 ch#0 pair, group#1 8, 9, 10, 11 group#2 16, 17, 18, 19, 20, 21, 22, 23 ch#0 pair, group#2 12, 13, 14, 15 group#3 24, 25, 26, 27, 28, 28, 30, 31 ch#0 pair, group#3 16, 17, 18, 19 group#4 0, 1, 2, 3, 4, 5, 6, 7, ch#1 pair, group#0 20, 21, 22, 23 group#5 8, 9, 10, 11, 12, 13, 14, 15 ch#1 pair, group#1 24, 25, 26, 27 group#6 16, 17, 18, 19, 20, 21, 22, 23 ch#1 pair, group#2 28, 29, 30, 31 group#7 24, 25, 26, 27, 28, 28, 30, 31 ch#1 pair, group#3 0, 1, 2, 3, 4, 5, 6, 7, ch#2 pair, group#0 8, 9, 10, 11, 12, 13, 14, 15 ch#2 pair, group#1 16, 17, 18, 19, 20, 21, 22, 23 ch#2 pair, group#2 24, 25, 26, 27, 28, 28, 30, 31 ch#2 pair, group#3
136 datasheet single channel mode multiple channel mode device-pair ids for group members group name device pair ids for group members group name 0, 1, 2, 3, 4, 5, 6, 7, ch#3 pair, group#0 8, 9, 10, 11, 12, 13, 14, 15 ch#3 pair, group#1 16, 17, 18, 19, 20, 21, 22, 23 ch#3 pair, group#2 24, 25, 26, 27, 28, 28, 30, 31 ch#3 pair, group#3 notes: 1. all rsl signals must be terminated at the far end from the mch. 2. the default device id for an rdram device after power up is 1fh. 5.3.1.2. rdram cmos signal description and usage there are 3 cmos signal pins per channel on the mch to support direct rdram device configuration, sio reset, register accesses, and nap and powerdown exits. these signals are sck, cmd and sio. they are used to perform the following operations: ? sio pin initialization ? sio operations (includes register accesses and device reset) ? device selection for nap and powerdown exits figure 8. rdram devices sideband cmos signal configuration on rambus* channel a rdram_cmos sio sio1 sio0 sio0 sck cmd sck cmd 82840 mch rambus channel a note: mch supports dual rambus direct channels. rdram rdram rdram rdram
82840 mch r datasheet 137 figure 9. mrh-r sideband cmos signal configuration on rambus* channel a rdram_cmos_mrh-r sio sio0 sck cmd sck cmd 82840 mch rambus channel a mrh-r table 17. sideband cmos signal description signal description sck serial clock: this signal serves as the clock for sio and cmd signals. sck is a clock source used for reading from and writing to control register. ? for sio operations and pin initialization, sck 1 mhz ? for power mode operations, sck 100 mhz cmd command: cmd is a control signal used for power mode transitions, sio pin configuration during initialization, and framing of sio operations. cmd is active high. this signal is sampled at both edges of sck and is a level sensitive signal. sio serial in out: this bi-directional signal is daisy chained through all direct rdram (sio0 to sio1) devices in a channel. this pin carries data used for sio operations that include register accesses, device reset, and device id initialization. sio is also used for power mode control. sio is an active low signal and is sampled on the falling edge of sck. table 18. cmd signal value decode sio = 0, cmd sample value on 4 sck edges sio = 1, cmd sample value on 4 sck edges cycle 0 cycle 1 command cycle 0 cycle 1 command 0 1 x x nap exit 0 1 x x power-down exit 1 0 x x reserved 1 0 x x reserved 0 0 x x no-op 0 0 x x no-op 1 1 1 1 sio request frame 1 1 1 1 sio request frame 1 1 0 0 sio reset 1 1 0 0 sio reset 1 1 1 0 reserved 1 1 1 0 reserved 1 1 0 1 reserved 1 1 0 1 reserved
138 datasheet sio pin initialization sio0 and sio1 pins on direct rdram devices are bi-directional; their direction needs to be initialized. the ?sio reset? initializes sio0 and sio1 pins on all direct rdrams as daisy chain configuration and is performed with sck and cmd. once the sio daisy chain is fully configured, sio operations can occur. note ?sio reset? does not reset the entire device. for a complete description of operation and associated timing diagram, refer to direct rdram data sheet from rambus*. sio operations sio operations are also known as direct rdram initialization operations. these operations include direct rdram register accesses and device reset, and are performed using the sck, cmd, sio0, and sio1 cmos pins. for a complete description of operation and associated timing diagram, refer to the direct rdram data sheet from rambus*. nap and powerdown exits the nap and power down exits are performed using cmd, sio and sck signals. for a complete description and timing diagrams associated with nap and powerdown exits, refer to direct rdram data sheet from rambus*. 5.3.1.3. direct rdram core refresh all rows in an direct rdram device must be refreshed within 32 ms. the refresh rate depends on the device size and page size of a device. mch supports two core refresh mechanisms: active refresh and self refresh. ? active refresh. refresh and precharge after refresh commands are issued from the primary control packet. these commands provide refresh support in standby/active modes. ? self refresh. internal timebase and row/bank address counters in the core provide allow for a self refresh in powerdown modes without controller support. 5.3.1.4. direct rdram current calibration all direct rdram devices must be current calibrated once every 100 ms. there are rsl commands to perform this function. the mch schedules periodic current calibration activity such that every device in the channel is current calibrated at least once every 100 ms. 5.3.2. direct rdram command encoding the operations on a direct rdram channel are performed using control packets. there are two types of command packets?row(rowa/rowr) packet and column (colc/colm/colx) packet. each command packet requires 4 direct rdram clock duration and packet data is transferred on both (leading and falling) edges of the clock. a row packet contains 24 bits and column packet contains 40 bits.
82840 mch r datasheet 139 5.3.2.1. row packet (rowa/rowr) the row packet is defined using three rsl signals rq[7:5]/row[2:0]. the row packet is generally the first control packet issued to a device. major characteristics of a row packet are: ? the only way to activate (sense) a row within a bank ? independent of direct rdram?s active/standby state ? a non-broadcast row package causes an addressed direct rdram to move to active state the packet definition of row packet is provided in the following table. table 19. rowa packet for activating (sensing) a row (i.e., av = 1) row # cycle 0 cycle 1 cycle 2 cycle 3 row2 dr4t dr[2] br[0] br[3] r[10] r[8] r[5] r[2] row1 dr4f d[r1] br[1] br[4] r[9] r[7] r[4] r[1] row0 dr[3] dr[0] br[2] rev av = 1 r[6] r[3] r[0] table 20. rowr packet for other operations (i.e., av = 0) row # cycle 0 cycle 1 cycle 2 cycle 3 row2 dr4t dr[2] br[0] br[3] rop[10] rop[8] rop[5] rop[2] row1 dr4f dr[1] br[1] br[4] rop[9] rop[7] rop[4] rop[1] row0 dr[3] dr[0] br[2] rev av = 0 rop[6] rop[3] rop[0] dr4t dr4f device id 0 0 no row packet 0 1 dr[3:0], dr[4] = 0 1 0 dr[3:0], dr[4] = 1 1 1 broadcast dr[4] ? dr[0] device address br[5] ? br[0] bank address r[10] ? r[0] row address av select between rowa and rowr, active row rop[10] ? rop[0] opcode for primary control packet rev reserved
140 datasheet opcode bits av 10 9 8 7 6 5 4 3 2: 0 operation description 1 x x x x x x x x xxx activate row 0 1 1 0 0 0 0 0 0 000 precharge 0 1 1 0 0 0 0 0 1 000 precharge & relax 0 0 0 0 1 1 0 0 0 000 refresh 0 1 0 1 0 1 0 0 0 000 precharge postrefresh 0 0 0 0 0 0 1 0 0 000 nap 0 0 0 0 0 0 1 1 0 000 conditional nap 0 0 0 0 0 0 0 1 0 000 power down 0 0 0 0 0 0 0 0 1 000 relax 0 0 0 0 0 0 0 0 0 010 temp calibration enable 0 0 0 0 0 0 0 0 0 001 temp calibration 0 0 0 0 0 0 0 0 0 000 no-op legend: x = controller drives 0 or 1 0 = controller drives 0 1 = controller drives 1
82840 mch r datasheet 141 5.3.2.2. column packet (colc/colx) the column packet is defined using five of the rsl signals rq[4:0]/col[4:0]. major characteristics of column are: ? the only way to dispatch column operation for read or write ? requires the target direct rdram to be in active state note: when an direct rdram is in active state, it can receive both row and column packets. when a direct rdram is in standby state, it can only receive a row packet. thus, before sending a column packet, make sure the addressed direct rdram is in active state. the packet definition of column packet is provided below. table 21. colc packet col # cycle 0 cycle 1 cycle 2 cycle 3 col4 dc[4] s = 1 c[6] c[4] col3 dc[3] c[5] c[3] col2 dc[2] cop[1] rev bc[2] c[2] col1 dc[1] cop[0] bc[4] bc[1] c[1] col0 dc[0] cop[2] cop[3] bc[3] bc[0] c[0] dc[4:0] device id for column operation s start bit, for framing m mask bit. asserted indicates mask format for packet cop[3:0] column operation code c[6:0] address for column operation bc[4:0] bank address for column operation rev reserved table 22. colc packet field encodings s cop[3] cop[2] cop[1] cop[0] command operation 0 x x x x no operation 1 x 0 0 0 nocop. retire write buffer of this device 1 x 0 0 1 write 1 x 0 1 1 read notes: all other combination are reserved
142 datasheet table 23. colx packet (m = 0) cycle 0 cycle 1 cycle 2 cycle 3 col4 dx[4] xop[4] rev bx[1] col3 m = 0 dx[3] xop[3] bx[4] bx[0] col2 dx[2] xop[2] bx[3] col1 dx[1] xop[1] bx[2] col0 dx[0] xop[0] dx[4:0] device id for extra operation bx[4:0] bank address for extra operation ma[7:0] byte mask (low order) mb[7:0] byte mask (high order) xop[4:0] opcode for extra operation rev reserved table 24. colm packet and colx packet field encodings m xop bits operation description 4 3 2 1 0 1 x x x x x non existent xop 0 0 0 0 0 0 noxop 0 1 0 0 0 0 reserved 0 0 1 0 0 0 calibrate current 0 0 1 1 0 0 calibrate current & sample 0 0 0 0 0 1 reserved legend: x = controller drives 0 or 1 0 = controller drives 0 1 = controller drives 1 5.3.2.3. data packet table 25. data packet cycle 0 cycle 1 cycle 2 cycle 3 dqa[8:0] da0[8:0] da1[8:0] da2[8:0] da3[8:0] da4[8:0] da5[8:0] da6[8:0] da7[8:0] dqb[8:0] db0[8:0] db1[8:0] db2[8:0] db3[8:0] db4[8:0] db5[8:0] db6[8:0] db7[8:0]
82840 mch r datasheet 143 5.3.3. direct rdram register programming software can read and write direct rdram device registers by programming the rdram initialization control management (ricm) register in the mch. the register data returned by the device will be available in the device register data (drd) register. 5.3.4. direct rdram operating states the direct rdram devices support different operating and idle states to minimize the power consumption and thermal overload. table 26 provides an overview of the different operating/power states supported by direct rdrams. table 26. dram operating states direct rdram state functionality refresh scheme rdram clock state inactive states powerdown no operation allowed except refresh. direct rdram awaits cmos signals to exit powerdown state self refresh stopped nap no operation allowed except refresh. direct rdram awaits nap exit command to exit nap active refresh stopped active states standby device ready to receive row packet . with fast clock active refresh full speed active device ready to receive any control packet active refresh full speed active-read device ready to receive any control packet. transmitting data on channel active refresh full speed active-write device ready to receive any control packet. receiving data from channel active refresh full speed active-read/write state a direct rdram device is in active-read/write state when it is transferring data. this state lasts as long as the data transfer is occurring. once the data transfer is done, the direct rdram transitions into active or standby state based on the column command last executed. active state a direct rdram enters into active state immediately after the data transfer from/to that device is done and the last colc command that caused the data transfer does not have its rc bit set to 1. when a device is in active state, it can accept both row and column packets. standby state a direct rdram enters into standby state either from active-read/write or active state. transition from active-read/write to standby happens if the last column executed has its rc bit set to 1. transition from active to standby happens if colc or row specifies an operation with relax. when a
144 datasheet device is in standby mode, it can accept only row packets. once a device receives any row packet, it transitions into active state and then can accept a column packet. nap state a direct rdram enters into nap state when it receives a row packet that specified an operation with nap. no operations except refresh is allowed during nap state. powerdown state a direct rdram enters into powerdown state when it receives a row packet which specified an operation with powerdown. no operations, except self-refresh, are allowed during powerdown state. rdram operating pools to minimize the operating power, the rdram devices are grouped into two operating pools called pool ?a? and pool ?b?. pool ?a? and pool ?b? operation in the ?pool? mode, two queues are used inside the mch: pool ?a? contains references to device pairs that are currently in the active mode while pool ?b? contains references to device pairs that are in the standby mode. all devices that are found in neither pool are either napping or standby. pool ?a? may hold between 1 and 8 device pairs, while pool ?b? may be configured to contain between 1 and 16 device pairs. 5.3.5. rdram power management 82840 mch systems support acpi based power management. the mch puts all rdram devices into powerdown (pd) state during s3 power management states. to enter the powerdown state all rdram devices in the channel must be in active or standby state. the mch then sends a broadcast powerdown command to that channel. during powerdown state, rdram devices are put into self refresh mode so that external (active) refreshes are not required. during the powerdown state, the clocks to rdram are shut off. exiting the powerdown and nap states are done through cmos signals. table 27 shows the actions taken by mch during different processor and system power states. table 27. rdram power management states processor state system state state of rdrams in pool ?a? state of rdrams in pool ?b? state of rdrams in pool ?c? refresh scheme rdram clock state c0, c1, c2 (processor in working state) s0 active- read/write, active standby nap or standby active running (processor in inactive state) s1, s3( str) no devices in pool ?a? no devices in pool ?b? powerdown self stopped
82840 mch r datasheet 145 5.3.6. data integrity the mch supports an error correcting code (or error checking and correcting) on the main memory interface. the mch can optionally be configured to generate the ecc code for writes to memory and check the code for reads from memory. the mch generates an 8-bit code word for each 64-bit qword of memory. since the code word covers a full qword, writes of less than a qword require a read-merge- write operation. consider a dword write to memory. in this case, when in ecc mode, the mch will read the qword where the addressed dword will be written, merge in the new dword, generate a code covering the new qword and finally write the entire qword and code back to memory. any correctable (single) errors detected during the initial qword read are corrected before merging the new dword. error scrubbing is supported by the mch. when enabled, this feature not only corrects single bit error data being returned to the requesting agent but also writes the corrected value back to the dram array. single-bit and multiple-bit errors set separate flags in the errsts register. single-bit errors and mutiple-bit errors can be independently enabled to generate hub interface serr, smi, or sci special cycles to the ich. the address and syndrome of the first single bit error are latched in the eap and derrctl registers. subsequent single bit errors do not overwrite the eap and derrctl registers unless the single-bit error status bit is cleared. a multiple-bit error overwrites the eap and derrctl registers. subsequent multiple-bit errors do not overwrite the eap and derrctl registers, unless the multiple-bit error status bit is cleared. 5.3.7. rdram array thermal management the rdram thermal and power management functions of the 82840 mch have been optimized for workstation and server system designs. it is assumed that proper system design will always provide and ensure adequate cooling in a 82840 chipset based system. the failsafe mechanism that protects the devices in the event of a catastrophic failure requires an external thermal sensor. when the thermal sensor is activated, the mch immediately exits the ?all devices on? mode and reverts the pool mode that has been programmed by system software. in a 82840-based system, rdram operates in one of three modes: active, standby, or nap. the number of devices allowed in each state at any given time is dictated by the heat dissipation budget specified by the system designer. from 1 to 8 device-pairs may be in pool ?a? and are configured to operate in the active mode. in addition, from 1 to 16 device-pairs may be in pool ?b? and are configured to operate in the standby mode. the rest of the device-pairs are in pool ?c? and may be configured to operate in either nap mode or standby mode. regardless of how many devices are configured into pool ?a? and pool ?b? or whether the pool ?c? devices are in napping or standby mode, the system designer is responsible for providing adequate cooling for the number of rdram devices in the system. after bios loads the system?s ?target? values into the dps register and initializes the pools, it should load a ?safer? set of values into the dps register without setting the poolinit field. the poolinit bit instructs the mch to transition to the new pool sizes. there are two other conditions that cause the 82840 mch to resize and initialize the pools: ? the transition of the overt# pin from electrical 1 to electrical 0 ? the detection of an overtemperature condition on any rdram device the overt# method is intended to allow system designers to use external thermal sensors to monitors the system temperature and assert overt# when system temperature exceeds system specifications. when the 82840 mch detects a falling edge on the overt# signal, it reinitializes and resizes the pools with whatever values are in the dps register. also, the rdram devices report overtemperature
146 datasheet conditions back to the mch via a special bit asserted during their current calibration operations. when the mch detects an overtemperature condition in any of the memory devices, the rdram pools are reinitialized with ?safer? values. finally, the mch may be configured to send an serr, sci, or smi hub interface message to ich. the software may take action to cool the system or to log the condition. 5.4. system reset the reset scheme for 82840 mch is shown in figure 10. after pwrok is asserted to indicate the system power is stable, rstin# is generated by ich and is used as an input to reset the mch. the mch always asserts cpurst#, if rstin# is asserted. the assertion of cpurst# resets the processors, as well as itp. cpurst# is deasserted synchronous to the host bus clock. figure 10. 82840 mch reset reset_overview itp mch cpurst# rstin# ich pcirst# init# pwrok pwrgood itp_rst# init# processor reset# pwrgood notes: the diagram does not represent all the details for schematics connection.
82840 mch r datasheet 147 6. ballout and package information 6.1. mch ball list the following two figures show a fooprint of the mch ballout with the signals indicated for each ball location. table 28 provides an alphabetical ball list.
148 datasheet figure 11. mch ballout (top view, left side) 1 2 3 4 5 6 7 8 9 10 11 12 13 a agprcomp agpref gad8 vcc1_8 clk66 gframe# gad17 gc/be3# gad25 gad30 sba4 sba2 rbf# b gad3 gad7 gc/be0# gad12 vss gdevsel# vss gad21 gad24 vss sba5 vss pipe# c gad2 gad6 vddq vss gpar gtrdy# gad18 vddq adstb1 gad29 sbstb# sba3 vddq d gad1 vss adstb0 gad11 g/cbe1# gstop# gc/be2# gad22 adstb1# gad28 sba6 sbstb wbf# e gad0 gad5 adstb0# gad10 gad15 vss gad16 gad19 vss gad27 sba7 vss sba0 f vss gad4 vss gad9 gad14 gserr# girdy# gad20 gad23 gad26 gad31 vddq sba1 g cha_dqa8 vss cha_dqa7 vss gad13 vddq vddq vddq vddq vcc1_8 h cha_dqa6 vss cha_dqa5 vss vss vddq vcc1_8 j cha_dqa2 cha_dqa4 cha_dqa3 vss vss vcc1_8 vcc1_8 k cha_dqa0 vss cha_dqa1 vss vss vcc1_8 vcc1_8 l cha_cfm cha_cfm# vss vss vss vcc1_8 vcc1_8 vcc1_8 vss m cha_ctm# cha_ctm vss vss vss vcc1_8 vcc1_8 vss vss n cha_rq6 vss cha_rq7 vss vss cha_ref0 vss vss vss p cha_rq5 cha_exp1 cha_exp0 vss vss cha_ref1 vss vss vss r cha_rq4 vss cha_rq3 vss vss vcc1_8 vcc1_8 vss vss t cha_rq2 cha_rq1 cha_rq0 vss vss vcc1_8 vcc1_8 vcc1_8 vss u cha_dqb1 vss cha_dqb0 vss vss vcc1_8 vcc1_8 v cha_dqb3 cha_dqb6 cha_dqb2 vss vss vcc1_8 vcc1_8 w cha_dqb5 vss cha_dqb4 vss vss nc vcc1_8 y cha_dqb7 vss cha_dqb8 vss vss vcc1_8 vcc1_8 vcc1_8 vcc1_8 vcc1_8 aa vss vss vss cmda scka overt# vcc1_8 vcc1_8 vcc1_8 vcc1_8 vcc1_8 vcc1_8 chb_ref0 ab rclkouta sioa dclkouta hlapd0 vss rstin# vss vss vss vss vss vss vss ac hlapd3 vss hla11 hlapd2 hlapd1 test# vss vss vss vss vss vss vss ad hla8 hlastb# hlastb vss dclkoutb vss chb_dqa7 chb_dqa5 chb_dqa3 chb_dqa1 vss vss chb_rq7 ae hlapd6 vss hla10 hlapd4 hla9 vss vss vss chb_dqa4 vss chb_cfm# chb_ctm vss af hlapd7 hlapd5 hlaref hlazcomp rclkoutb vss chb_dqa8 chb_dqa6 chb_dqa2 chb_dqa0 chb_cfm chb_ctm# chb_rq6 1 2 3 4 5 6 7 8 9 10 11 12 13
82840 mch r datasheet 149 figure 12. mch ballout (top view, right side) 14 15 16 17 18 19 20 21 22 23 24 25 26 greq# hlbstb0# hlbstb0 hlb17 hlbpd9 hlbrcomp ierr# gtlrefa vcc1_8 vss dep2# dep4# dep0# a ggnt# vss hlbpd4 vss hlbpd10 vss hlbref dep1# hclkin dep3# dep7# vss dep5# b st0 hlbpd1 hlbpd5 hlb19 hlbpd11 hlbpd13 dep6# hd61# vss hd62# hd58# hd63# hd55# c st1 hlbpd2 hlbpd6 hlb16 hlbstb1# hlbpd14 hd60# hd53# hd57# hd56# hd50# hd54# hd46# d st2 vss hlbpd7 vss hlbstb1 vss hd49# vss hd51# hd59# hd48# vss hd42# e hlbpd0 hlbpd3 hlb18 hlbpd8 hlbpd12 hlbpd15 hd45# hd39# hd52# vss hd41# hd47# hd43# f vcc1_8 vcc1_8 vcc1_8 vss hd37# hd33# hd44# hd36# hd40# hd35# g vtt hd31# vss hd34# hd38# vss hd30# h vtt hd27# hd24# hd32# hd28# hd29# hd23# j vtt hd21# hd16# hd26# hd25# hd22# hd13# k vss vcc1_8 vcc1_8 hd11# vss hd19# hd18# vss hd10# l vss vss vcc1_8 hd14# hd9# hd20# hd17# hd15# hd8# m vss vss vss hd5# hd3# hd12# hd7# hd6# hd1# n vss vss vss berr# vss hd4# hd2# vss ha33# p vss vss vcc1_8 ha34# ha30# hd0# cpurst# ha35# ha32# r vss vcc1_8 vcc1_8 ha31# ha27# ha22# ha29# ha26# ha24# t vtt ha23# vss ha19# ha28# vss ha20# u vtt ha18# ha16# ha13# ha21# ha25# ha15# v vtt ha14# ha10# ha5# ha17# ha11# ha12# w vcc1_8 vcc1_8 vcc1_8 vss ha9# vss ha4# ha8# vss ha7# y chb_ref1 vcc1_8 vcc1_8 vcc1_8 vcc1_8 vcc1_8 vcc1_8 bnr# bpri# ha3# ha6# hreq0# htrdy# aa vss vss vss vss vss vss vss sckb defer# hreq1# hreq4# hlock# hreq2# ab vss vss vss vss vss vss vss cmdb vss hreq3# drdy# vss hitm# ac chb_exp0 chb_rq3 chb_rq0 chb_dqb0 chb_dqb2 chb_dqb4 chb_dqb8 vss dbsy# rs0# hit# rs2# rp# ad chb_exp1 vss chb_rq1 vss chb_dqb6 vss vss vss siob vss rsp# vss ads# ae chb_rq5 chb_rq4 chb_rq2 chb_dqb1 chb_dqb3 chb_dqb5 chb_dqb7 vss gtlrefb rs1# breq0# ap0# ap1# af 14 15 16 17 18 19 20 21 22 23 24 25 26
150 datasheet table 28. mch alphabetical ballout list signal ball # ads# ae26 adstb0 d3 adstb0# e3 adstb1 c9 adstb1# d9 agprcomp a1 agpref a2 ap0# af25 ap1# af26 berr# p21 bnr# aa21 bpri# aa22 breq0# af24 cha_cfm l1 cha_cfm# l2 cha_ctm m2 cha_ctm# m1 cha_dqa0 k1 cha_dqa1 k3 cha_dqa2 j1 cha_dqa3 j3 cha_dqa4 j2 cha_dqa5 h3 cha_dqa6 h1 cha_dqa7 g3 cha_dqa8 g1 cha_dqb0 u3 cha_dqb1 u1 cha_dqb2 v3 cha_dqb3 v1 cha_dqb4 w3 cha_dqb5 w1 cha_dqb6 v2 cha_dqb7 y1 cha_dqb8 y3 signal ball # cha_exp0 p3 cha_exp1 p2 cha_ref0 n6 cha_ref1 p6 cha_rq0 t3 cha_rq1 t2 cha_rq2 t1 cha_rq3 r3 cha_rq4 r1 cha_rq5 p1 cha_rq6 n1 cha_rq7 n3 chb_cfm af11 chb_cfm# ae11 chb_ctm ae12 chb_ctm# af12 chb_dqa0 af10 chb_dqa1 ad10 chb_dqa2 af9 chb_dqa3 ad9 chb_dqa4 ae9 chb_dqa5 ad8 chb_dqa6 af8 chb_dqa7 ad7 chb_dqa8 af7 chb_dqb0 ad17 chb_dqb1 af17 chb_dqb2 ad18 chb_dqb3 af18 chb_dqb4 ad19 chb_dqb5 af19 chb_dqb6 ae18 chb_dqb7 af20 chb_dqb8 ad20 chb_exp0 ad14 signal ball # chb_exp1 ae14 chb_ref0 aa13 chb_ref1 aa14 chb_rq0 ad16 chb_rq1 ae16 chb_rq2 af16 chb_rq3 ad15 chb_rq4 af15 chb_rq5 af14 chb_rq6 af13 chb_rq7 ad13 clk66 a5 cmda aa4 cmdb ac21 cpurst# r24 dbsy# ad22 dclkouta ab3 dclkoutb ad5 defer# ab22 dep0# a26 dep1# b21 dep2# a24 dep3# b23 dep4# a25 dep5# b26 dep6# c20 dep7# b24 drdy# ac24 g/cbe1# d5 gad0 e1 gad1 d1 gad2 c1 gad3 b1 gad4 f2 gad5 e2 signal ball # gad6 c2 gad7 b2 gad8 a3 gad9 f4 gad10 e4 gad11 d4 gad12 b4 gad13 g5 gad14 f5 gad15 e5 gad16 e7 gad17 a7 gad18 c7 gad19 e8 gad20 f8 gad21 b8 gad22 d8 gad23 f9 gad24 b9 gad25 a9 gad26 f10 gad27 e10 gad28 d10 gad29 c10 gad30 a10 gad31 f11 gc/be0# b3 gc/be2# d7 gc/be3# a8 gdevsel# b6 gframe# a6 ggnt# b14 girdy# f7 gpar c5 greq# a14
82840 mch r datasheet 151 signal ball # gserr# f6 gstop# d6 gtlrefa a21 gtlrefb af22 gtrdy# c6 ha3# aa23 ha4# y23 ha5# w23 ha6# aa24 ha7# y26 ha8# y24 ha9# y21 ha10# w22 ha11# w25 ha12# w26 ha13# v23 ha14# w21 ha15# v26 ha16# v22 ha17# w24 ha18# v21 ha19# u23 ha20# u26 ha21# v24 ha22# t23 ha23# u21 ha24# t26 ha25# v25 ha26# t25 ha27# t22 ha28# u24 ha29# t24 ha30# r22 ha31# t21 ha32# r26 ha33# p26 signal ball # ha34# r21 ha35# r25 hclkin b22 hd00# r23 hd1# n26 hd2# p24 hd3# n22 hd4# p23 hd5# n21 hd6# n25 hd7# n24 hd8# m26 hd9# m22 hd10# l26 hd11# l21 hd12# n23 hd13# k26 hd14# m21 hd15# m25 hd16# k22 hd17# m24 hd18# l24 hd19# l23 hd20# m23 hd21# k21 hd22# k25 hd23# j26 hd24# j22 hd25# k24 hd26# k23 hd27# j21 hd28# j24 hd29# j25 hd30# h26 hd31# h21 hd32# j23 signal ball # hd33# g22 hd34# h23 hd35# g26 hd36# g24 hd37# g21 hd38# h24 hd39# f21 hd40# g25 hd41# f24 hd42# e26 hd43# f26 hd44# g23 hd45# f20 hd46# d26 hd47# f25 hd48# e24 hd49# e20 hd50# d24 hd51# e22 hd52# f22 hd53# d21 hd54# d25 hd55# c26 hd56# d23 hd57# d22 hd58# c24 hd59# e23 hd60# d20 hd61# c21 hd62# c23 hd63# c25 hit# ad24 hitm# ac26 hla8 ad1 hla9 ae5 hla10 ae3 signal ball # hla11 ac3 hlapd0 ab4 hlapd1 ac5 hlapd2 ac4 hlapd3 ac1 hlapd4 ae4 hlapd5 af2 hlapd6 ae1 hlapd7 af1 hlaref af3 hlastb ad3 hlastb# ad2 hlazcomp af4 hlb16 d17 hlb17 a17 hlb18 f16 hlb19 c17 hlbpd0 f14 hlbpd1 c15 hlbpd2 d15 hlbpd3 f15 hlbpd4 b16 hlbpd5 c16 hlbpd6 d16 hlbpd7 e16 hlbpd8 f17 hlbpd9 a18 hlbpd10 b18 hlbpd11 c18 hlbpd12 f18 hlbpd13 c19 hlbpd14 d19 hlbpd15 f19 hlbrcomp a19 hlbref b20 hlbstb0 a16
152 datasheet signal ball # hlbstb0# a15 hlbstb1 e18 hlbstb1# d18 hlock# ab25 hreq0# aa25 hreq1# ab23 hreq2# ab26 hreq3# ac23 hreq4# ab24 htrdy# aa26 ierr# a20 nc w6 overt# aa6 pipe# b13 rbf# a13 rclkouta ab1 rclkoutb af5 rp# ad26 rs0# ad23 rs1# af23 rs2# ad25 rsp# ae24 rstin# ab6 sba0 e13 sba1 f13 sba2 a12 sba3 c12 sba4 a11 sba5 b11 sba6 d11 sba7 e11 sbstb d12 sbstb# c11 scka aa5 sckb ab21 sioa ab2 signal ball # siob ae22 st0 c14 st1 d14 st2 e14 test# ac6 vcc1_8 w7 vcc1_8 y8 vcc1_8 y19 vcc1_8 aa8 vcc1_8 aa19 vcc1_8 aa20 vcc1_8 g10 vcc1_8 g17 vcc1_8 g18 vcc1_8 g19 vcc1_8 h7 vcc1_8 l11 vcc1_8 l12 vcc1_8 l15 vcc1_8 l16 vcc1_8 m11 vcc1_8 m16 vcc1_8 r6 vcc1_8 r11 vcc1_8 r16 vcc1_8 t11 vcc1_8 t12 vcc1_8 t15 vcc1_8 t16 vcc1_8 y6 vcc1_8 y7 vcc1_8 aa7 vcc1_8 aa15 vcc1_8 a4 vcc1_8 a22 vcc1_8 j6 signal ball # vcc1_8 j7 vcc1_8 k6 vcc1_8 k7 vcc1_8 l6 vcc1_8 m6 vcc1_8 t6 vcc1_8 u6 vcc1_8 u7 vcc1_8 v6 vcc1_8 v7 vcc1_8 y9 vcc1_8 y10 vcc1_8 y17 vcc1_8 y18 vcc1_8 aa9 vcc1_8 aa10 vcc1_8 aa11 vcc1_8 aa12 vcc1_8 aa16 vcc1_8 aa17 vcc1_8 aa18 vddq c3 vddq c8 vddq c13 vddq f12 vddq g6 vddq g7 vddq g8 vddq g9 vddq h6 vss a23 vss b5 vss b7 vss b10 vss b12 vss b15 signal ball # vss b17 vss b19 vss b25 vss c4 vss c22 vss d2 vss e6 vss e9 vss e12 vss e15 vss e17 vss e19 vss e21 vss e25 vss f1 vss f3 vss f23 vss g2 vss g4 vss g20 vss h2 vss h4 vss h5 vss h22 vss h25 vss j4 vss j5 vss k2 vss k4 vss k5 vss l3 vss l4 vss l5 vss l13 vss l14 vss l22
82840 mch r datasheet 153 signal ball # vss l25 vss m3 vss m4 vss m5 vss m12 vss m13 vss m14 vss m15 vss n2 vss n4 vss n5 vss n11 vss n12 vss n13 vss n14 vss n15 vss n16 vss p4 vss p5 vss p11 vss p12 vss p13 vss p14 vss p15 vss p16 vss p22 vss p25 vss r2 vss r4 vss r5 vss r12 vss r13 vss r14 vss r15 vss t4 vss t5 signal ball # vss t13 vss t14 vss u2 vss u4 vss u5 vss u22 vss u25 vss v4 vss v5 vss w2 vss w4 vss w5 vss y2 vss y4 vss y5 vss y20 vss y22 vss y25 vss aa1 vss aa2 vss aa3 vss ab5 vss ab7 vss ab8 vss ab9 vss ab10 vss ab11 vss ab12 vss ab13 vss ab14 vss ab15 vss ab16 vss ab17 vss ab18 vss ab19 vss ab20 signal ball # vss ac2 vss ac7 vss ac8 vss ac9 vss ac10 vss ac11 vss ac12 vss ac13 vss ac14 vss ac15 vss ac16 vss ac17 vss ac18 vss ac19 vss ac20 vss ac22 vss ac25 vss ad4 vss ad6 vss ad11 vss ad12 vss ad21 vss ae2 vss ae6 vss ae7 vss ae8 vss ae10 vss ae13 vss ae15 vss ae17 vss ae19 vss ae20 vss ae21 vss ae23 vss ae25 vss af6 signal ball # vss af21 vtt h20 vtt j20 vtt k20 vtt u20 vtt v20 vtt w20 wbf# d13
154 datasheet 6.2. package information this specification outlines the mechanical dimensions for the 82840 mch. the package is a 544 ball grid array (bga). figure 13. 82840 mch bga package dimensions (top and side views) pin a1 i.d. pin a1 corner d d1 e e1 top view a a2 a1 c side view pkgbga_top&side.vsd seating plane -c- 45 chamfer (4 places) 30
82840 mch r datasheet 155 figure 14. 82840 mch bga package dimensions (bottom view) pkgbga_544 pin a1 corner e 544 bga bottom view 2 10 16 20 22 3 5 7 9 11 13 15 17 19 1 21 23 4 6 18 8 12 14 a b c d e f g h j k l p r t u v y ab aa ac n w m j l e b 24 25 26 ad ae af table 29. package dimensions symbol min nominal max units note a 2.17 2.38 2.59 mm a1 0.50 0.60 0.70 mm a2 1.12 1.17 1.22 mm d 34.80 35.00 35.20 mm d1 29.75 30.00 30.25 mm e 34.80 35.00 35.20 mm e1 29.75 30.00 30.25 mm e 1.27 (solder ball pitch) mm i 1.63 ref. mm j 1.63 ref. mm m 26 x 26 matrix mm b 2 0.60 0.75 0.90 mm c 0.55 0.61 0.67 mm notes: 1. all dimensions and tolerances conform to ansi y14.5-1982 2. dimension is measured at maximum solder ball diameter parallel to primary datum (-c-) 3. primary datum (-c-) and seating plane are defined by the spherical crowns of the solder balls.
156 datasheet 6.2.1. 82840 rsl nomalized trace length data expansion channel a ? ? ? ? l pkg normalized to cha_dqa8 expansion channel b ? ? ? ? l pkg normalized to chb_dqb7 signal ball ? ? ? ? l pkg (mils) signal ball ? ? ? ? l pkg (mils) cha_cfm l1 102.756 chb_cfm af11 103.543 cha_ cfm# l2 118.897 chb_ cfm# ae11 110.630 cha_ctm m2 130.315 chb_ctm ae12 109.842 cha_ctm# m1 117.716 chb_ctm# af12 110.236 cha_dqa0 k1 93.701 chb_dqa0 af10 101.968 cha_ dqa1 k3 162.204 chb_ dqa1 ad10 150.393 cha_ dqa2 j1 40.551 chb_ dqa2 af9 81.102 cha_ dqa3 j3 137.008 chb_ dqa3 ad9 137.401 cha_ dqa4 j2 87.795 chb_ dqa4 ae9 115.354 cha_ dqa5 h3 115.748 chb_ dqa5 ad8 120.079 cha_ dqa6 h1 61.811 chb_ dqa6 af8 48.425 cha_ dqa7 g3 99.212 chb_ dqa7 ad7 109.055 cha_dqa8 g1 0.000 chb_dqa8 af7 29.921 cha_dqb0 u3 143.307 chb_dqb0 ad17 130.708 cha_ dqb1 u1 122.441 chb_ dqb1 af17 72.441 cha_ dqb2 v3 164.173 chb_ dqb2 ad18 120.079 cha_ dqb3 v1 111.417 chb_ dqb3 af18 69.291 cha_ dqb4 w3 151.181 chb_ dqb4 ad19 142.126 cha_ dqb5 w1 68.504 chb_ dqb5 af19 34.252 cha_ dqb6 v2 106.693 chb_ dqb6 ae18 111.417 cha_ dqb7 y1 40.157 chb_ dqb7 af20 0.000 cha_ dqb8 y3 134.252 chb_ dqb8 ad20 70.472 cha_exp0 p3 192.519 chb_exp0 ad14 160.236 cha_exp1 p2 129.921 chb_exp1 ae14 161.811 cha_rq0 t3 185.433 chb_rq0 ad16 152.362 cha_ rq1 t2 131.496 chb_ rq1 ae16 93.307 cha_ rq2 t1 126.378 chb_ rq2 af16 98.425 cha_ rq3 r3 189.370 chb_ rq3 ad15 157.480 cha_ rq4 r1 85.039 chb_ rq4 af15 106.693 cha_ rq5 p1 78.740 chb_ rq5 af14 101.968 cha_ rq6 n1 124.409 chb_ rq6 af13 112.205 cha_ rq7 n3 175.984 chb_ rq7 ad13 161.811
82840 mch r datasheet 157 these lengths must be considered when matching trace lengths as described in the intel ? 840 chipset design guide . note that these lengths are normalized to 0 with the longest trace on the package. they do not represent the actual lengths from pad to ball. the following formula is used to determine ? l pcb ? l pcb = ( ? l pkg *v pkg ) / v pcb where: ? l pcb is the nominal ? pcb trace length to be added on the pcb ? l pkg is the nominal ? package trace length. v pkg is the package trace velocity, and the nominal value is 180 ps/in v pcb is the pcb trace velocity the data given can be renormalized to start routing from a different ball. if a different rsl signal (other than longest trace) is used for nominalization, simply use the following equation: new ? l pkg ' = ? l pkg - ? l rsl for example: for the mch, if mch cha_cfm trace length is used for nominalization, then: signal ? ? ? ? l pkg (mils) new ? ? ? ? l pkg (mils) cha_cfm 102.756 0.000 cha_cfm# 118.897 16.142 cha_ctm 130.315 27.559 : : : : : : cha_rq6 124.409 21.653 cha_rq7 175.984 73.228
158 datasheet this page is intentionally left blank.
82840 mch r datasheet 159 7. testability in the mch, the testability for automated test equipment (ate) board level testing has been changed from traditional nand chain to the new xor chain. an xor-tree is a chain of xor gates, each with one input pin connected to it as shown in figure 15. the first xor gate should have one pin connected to vcc1_8. figure 15. xor-tree chain input xor out xor.vsd input input input input vcc1_8 the algorithm used for in-circuit test is as follows: ? drive ?0? onto all input pins. this, along with the first xor gate having one input connected to vcc1_8 and the outputs being non-inverting, consistently produces a ?1? at ?xor out?, regardless of how many xor gates are in the chain. ? drive each input pin one at a time, first to a ?1? and then back to a ?0?. this causes ?xor out? first to produce a ?0? and then a ?1?. ? the output pins can now be checked by driving a ?0? onto the pin of the xor gate that has its second input to the xor gate connected to gnd and then back to a ?1?. the output pins will go to a ?0? and then back to a ?1?. the above algorithm is for all pins properly soldered to the board under test and no pins connected to a power plane. if there is an even number of total signal pins connected to a power plane or unsoldered and floating to a ?1? logic level, then the following would happen: ? drive ?0? onto all other input and bi-directional pins. ?xor out? would start out at a ?1? level instead of a ?0?. ? drive each input or bi-directional pin, one at a time, first to a ?1? and then back to a ?0.? this causes ?xor out? first to produce a ?0? and then a ?1?. a flexible test model used for in-circuit test will need to determine if ?xor out? initially is a ?0? or ?1? level. one at a time, each input or bi-directional pin is driven to ?1? and then back to a ?0.? the ?xor out? will first toggle to the opposite state that was initially determined and then toggle back to the initially determined state. any unsoldered pin will cause ?xor out? not to toggle.
160 datasheet 7.1. initialization sequence two pins are used to enter the xor chain test mode as shown in the figure 16. xor chain test mode entering rules: ? test# should be driven ?low? for exactly 7 clocks after ?rstin#? goes ?high? (inactive). ? once test# is driven ?low? for exactly 7 clocks and then ?high?, it will ?lock? in the xor chain test mode. ? test# should never be driven in the ?low? state other than driven ?low? for 7 clocks to enter the xor chain test mode. if test# goes ?low? for a moment because of a glitch, the mch needs to be ?reset? for going to normal operation or entering the xor chain test mode again. figure 16. xor chain test mode initialization clk66 rstin# any number of clocks between 16 and 64 1234 6 57 test# minimum 10 clocks exactly 7 clocks "lock" in the xor chain test mode to enter the xor chain test mode, drive test# low for exactly 7 clk66 clocks after rstin# is high (inactive). test_init
82840 mch r datasheet 161 7.2. xor chains table 30. xor chain #0 connections name ball chain element # note gc/be1# d5 1 input gserr# f6 2 gad_15 e5 3 gc/be0# b3 4 gad_11 d4 5 gad_14 f5 6 gad_7 b2 7 gad_10 e4 8 gad_13 g5 9 gad_6 c2 10 adstb0 d3 11 gad_2 c1 12 gad_5 e2 13 gad_1 d1 14 gad_4 f2 15 gad_0 e1 16 gad_9 f4 17 gad_8 a3 18 gad_12 b4 19 gad_3 b1 20 cha_sio ab2 21 cha_cmd aa4 22 cha_sck aa5 23 hclkouta ab3 24 rclkouta ab1 25 hla11 ac3 26 hla8 ad1 27 hla3 ac1 28 hla0 ab4 29 hla6 ae1 30 hla2 ac4 31 hlastb ad3 32 hlastb# ad2 33 hla7 af1 34 hla1 ac5 35 hla5 af2 36 table 30. xor chain #0 connections name ball chain element # note hla4 ae4 37 hla10 ae3 38 hlazcomp af4 39 hla9 ae5 40 test# ac6 41 overt# aa6 42 hclkoutb ad5 43 rclkoutb af5 44 output table 31. xor chain #1 connections name ball chain element # note adstb0# e3 1 input chb_sck ab21 2 chb_cmd ac21 3 chb_sio ae22 4 rs1# af23 5 dbsy# ad22 6 breq0# af24 7 rsp# ae24 8 ap0# af25 9 rs0# ad23 10 rp# ad26 11 ads# ae26 12 hit# ad24 13 hreq3# ac23 14 rs2# ad25 15 drdy# ac24 16 defer# ab22 17 hitm# ac26 18 hreq1# ab23 19 bnr# aa21 20 hreq4# ab24 21 bpri# aa22 22 ap1# af26 23 output
162 datasheet table 32. xor chain #2 connections name ball chain element # note ha3# aa23 1 input hlock# ab25 2 ha6# aa24 3 hreq2# ab26 4 ha4# y23 5 hreq0# aa25 6 ha8# y24 7 htrdy# aa26 8 ha5# w23 9 ha17# w24 10 ha11# w25 11 ha7# y26 12 ha13# v23 13 ha21# v24 14 ha12# w26 15 ha9# y21 16 ha14# w21 17 ha25# v25 18 ha19# u23 19 ha10# w22 20 ha15# v26 21 ha18# v21 22 ha28# u24 23 ha20# u26 24 ha22# t23 25 ha16# v22 26 ha26# t25 27 ha29# t24 28 ha24# t26 29 hd0# r23 30 hd2# p24 31 cpurst# r24 32 ha23# u21 33 ha35# r25 34 ha32# r26 35 ha31# t21 36 ha33# p26 37 hd4# p23 38 hd1# n26 39 table 32. xor chain #2 connections name ball chain element # note ha27# t22 40 hd6# n25 41 hd7# n24 42 hd12# n23 43 ha34# r21 44 ha30# r22 45 hd8# m26 46 hd19# l23 47 hd15# m25 48 hd17# m24 49 berr# p21 50 hd10# l26 51 hd20# m23 52 hd3# n22 53 hd13# k26 54 hd18# l24 55 hd5# n21 56 hd22# k25 57 hd23# j26 58 sbstb d12 59 adstb1 c9 60 output table 33. xor chain #3 connections name ball chain element # note hd25# k24 1 input hd9# m22 2 hd29# j25 3 hd30# h26 4 hd14# m21 5 hd26# k23 6 hd28# j24 7 hd11# l21 8 hd35# g26 9 hd40# g25 10 hd43# f26 11 hd47# f25 12 hd16# k22 13 hd21# k21 14
82840 mch r datasheet 163 table 33. xor chain #3 connections name ball chain element # note hd41# f24 15 hd32# j23 16 hd24# j22 17 hd27# j21 18 hd38# h24 19 hd36# g24 20 hd42# e26 21 hd34# h23 22 hd46# d26 23 hd54# d25 24 hd31# h21 25 hd48# e24 26 hd50# d24 27 hd44# g23 28 hd55# c26 29 hd59# e23 30 hd56# d23 31 hd63# c25 32 hd33# g22 33 hd37# g21 34 hd58# c24 35 dep5# b26 36 hd52# f22 37 hd62# c23 38 hd51# e22 39 dep7# b24 40 dep0# a26 41 dep4# a25 42 dep2# a24 43 hd39# f21 44 hd57# d22 45 dep3# b23 46 hd45# f20 47 hd53# d21 48 hd61# c21 49 hd49# e20 50 dep1# b21 51 hd60# d20 52 dep6# c20 53 ierr# a20 54 output table 34. xor chain #4 connections name ball chain element # note hlbzcomp a19 1 input hlb15 f19 2 hlb14 d19 3 hlb13 c19 4 hlb12 f18 5 hlbstb1 e18 6 hlbstb1# d18 7 hlb11 c18 8 hlb10 b18 9 hlb9 a18 10 hlb8 f17 11 hlb16 d17 12 hlb19 c17 13 hlb17 a17 14 hlb18 f16 15 hlb7 e16 16 hlb6 d16 17 hlb5 c16 18 hlb4 b16 19 hlbstb0 a16 20 hlbstb0# a15 21 hlb3 f15 22 hlb2 d15 23 hlb1 c15 24 hlb0 f14 25 greq# a14 26 ggnt# b14 27 st_0 c14 28 st_1 d14 29 st_2 e14 30 rbf# a13 31 pipe# b13 32 wbf# d13 33 sbstb# c11 34 gad_30 a10 35 gad_25 a9 36 gad_29 c10 37 gad_24 b9 38 gc/be3# a8 39
164 datasheet table 34. xor chain #4 connections name ball chain element # note gad_28 d10 40 gad_21 b8 41 gad_31 f11 42 gad_27 e10 43 adstb1# d9 44 gad_17 a7 45 gad_26 f10 46 gad_22 d8 47 gad_18 c7 48 gc/be2# d7 49 gad_19 e8 50 gad_23 f9 51 gad_16 e7 52 gad_20 f8 53 gframe# a6 54 gdevsel# b6 55 gpar c5 56 gtrdy# c6 57 gstop# d6 58 girdy# f7 59 output table 35. xor chain #5 connections name ball chain element # note cha_dqa8 g1 1 input cha_dqa7 g3 2 cha_dqa6 h1 3 cha_dqa5 h3 4 cha_dqa4 j2 5 cha_dqa3 j3 6 cha_dqa2 j1 7 cha_dqa1 k3 8 cha_dqa0 k1 9 cha_cfm l1 10 cha_cfm# l2 11 cha_exp0 p3 12 cha_exp1 p2 13 cha_rq7 n3 14 cha_rq6 n1 15 table 35. xor chain #5 connections name ball chain element # note cha_rq5 p1 16 cha_rq4 r1 17 cha_rq3 r3 18 cha_rq2 t1 19 cha_rq1 t2 20 cha_rq0 t3 21 cha_dqb0 u3 22 cha_dqb1 u1 23 cha_dqb2 v3 24 cha_dqb3 v1 25 cha_dqb4 w3 26 cha_dqb5 w1 27 cha_dqb6 v2 28 cha_dqb7 y1 29 cha_dqb8 y3 30 sba_5 b11 31 output table 36. xor chain #6 connections name ball chain element # note chb_dqa8 af7 1 input chb_dqa7 ad7 2 chb_dqa6 af8 3 chb_dqa5 ad8 4 chb_dqa4 ae9 5 chb_dqa3 ad9 6 chb_dqa2 af9 7 chb_dqa1 ad10 8 chb_dqa0 af10 9 chb_cfm af11 10 chb_cfm# ae11 11 chb_exp0 ad14 12 chb_exp1 ae14 13 chb_rq7 ad13 14 chb_rq6 af13 15 chb_rq5 af14 16 chb_rq4 af15 17 chb_rq3 ad15 18 chb_rq2 af16 19
82840 mch r datasheet 165 table 36. xor chain #6 connections name ball chain element # note chb_rq1 ae16 20 chb_rq0 ad16 21 chb_dqb0 ad17 22 chb_dqb1 af17 23 chb_dqb2 ad18 24 chb_dqb3 af18 25 chb_dqb4 ad19 26 chb_dqb5 af19 27 chb_dqb6 ae18 28 chb_dqb7 af20 29 chb_dqb8 ad20 30 sba_7 e11 31 output
intel around the world united states and canada intel corporation robert noyce building 2200 mission college boulevard p.o. box 58119 santa clara, ca 95052-8119 usa phone: (800) 628-8686 europe intel corporation (u.k.) ltd. pipers way swindon wiltshire sn3 1rj uk phone: england (44) 1793 403 000 germany (49) 89 99143 0 france (33) 1 4571 7171 italy (39) 2 575 441 israel (972) 2 589 7111 netherlands (31) 10 286 6111 sweden (46) 8 705 5600 asia pacific intel semiconductor ltd. 32/f two pacific place 88 queensway, central hong kong, sar phone: (852) 2844 4555 japan intel kabushiki kaisha p.o. box 115 ts ukuba-gakuen 5-6 tokodai, tsukuba-shi ibaraki-ken 305 japan phone: (81) 298 47 8522 south america intel semicondutores do brazil rua florida 1703-2 and cj22 cep 04565-001 sao paulo-sp brazil phone: (55) 11 5505 2296 for more information to learn more about intel corporation, visit our site on the world wide web at www.intel.com r

▲Up To Search▲

Price & Availability of 298020-002

	To Download 298020-002 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .